Broken DB migrations since 8ca1078

Describe the bug
Sample data dump points to revision which doesn't exist:
https://github.com/Netflix/dispatch/blob/e975fbced396062bad2734b2b9fcba56223d2e6c/data/dispatch-sample-data.dump#L2417 points to dropped migration.
This prevents DB migrations from succeeding.
To Reproduce
Steps to reproduce the behavior:

Run ./install.sh from https://github.com/Netflix/dispatch-docker/blob/master/install.sh
Loading example data throws the error below
Skipping example data load will result in another error below

Expected behavior
Both flows should succeed
Additional context
Log for loading example data:
Do you want to load example data (WARNING: this will remove all existing database data) (y/N)?y
...
Example data loaded. Navigate to /register and create a new user.
Running standard database migrations...
Creating dispatch_core_1 ... done
Creating dispatch_web_run ... done
Detected single tenant database, converting to multi-tenant...
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute
    cursor.execute(statement, parameters)
psycopg2.errors.UndefinedTable: relation "dispatch_core.organization" does not exist

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

Traceback (most recent call last):
  File "/usr/local/bin/dispatch", line 8, in <module>
    sys.exit(entrypoint())
  File "/usr/local/lib/python3.8/site-packages/dispatch/cli.py", line 715, in entrypoint
    dispatch_cli()
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1137, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1062, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 763, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/dispatch/cli.py", line 369, in upgrade_database
    setup_fulltext_search(conn, get_core_tables())
  File "/usr/local/lib/python3.8/site-packages/dispatch/database/manage.py", line 164, in setup_fulltext_search
    sync_trigger(**trigger)
  File "/usr/local/lib/python3.8/site-packages/dispatch/search/fulltext/__init__.py", line 399, in sync_trigger
    conn.execute(str(sql), **sql.params)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1003, in execute
    return self._execute_text(object_, multiparams, params)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1172, in _execute_text
    ret = self._execute_context(
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context
    self._handle_dbapi_exception(
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception
    util.raise_(
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_
    raise exception
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedTable) relation "dispatch_core.organization" does not exist

[SQL: CREATE TRIGGER organization_search_vector_trigger BEFORE UPDATE OR INSERT ON dispatch_core."organization" FOR EACH ROW EXECUTE PROCEDURE organization_search_vector_update()]
(Background on this error at: http://sqlalche.me/e/13/f405)
ERROR: 1
Cleaning up...

Log for skipping the load:
Do you want to load example data (WARNING: this will remove all existing database data) (y/N)?N
Running standard database migrations...
Creating dispatch_core_1 ... done
Creating dispatch_web_run ... done
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 171, in _catch_revision_errors
    yield
  File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 365, in _upgrade_revs
    revs = list(revs)
  File "/usr/local/lib/python3.8/site-packages/alembic/script/revision.py", line 706, in iterate_revisions
    revisions, heads = fn(
  File "/usr/local/lib/python3.8/site-packages/alembic/script/revision.py", line 1290, in _collect_upgrade_revisions
    current_revisions = self.get_revisions(lower)
  File "/usr/local/lib/python3.8/site-packages/alembic/script/revision.py", line 457, in get_revisions
    return sum([self.get_revisions(id_elem) for id_elem in id_], ())
  File "/usr/local/lib/python3.8/site-packages/alembic/script/revision.py", line 457, in <listcomp>
    return sum([self.get_revisions(id_elem) for id_elem in id_], ())
  File "/usr/local/lib/python3.8/site-packages/alembic/script/revision.py", line 479, in get_revisions
    return tuple(
  File "/usr/local/lib/python3.8/site-packages/alembic/script/revision.py", line 480, in <genexpr>
    self._revision_for_ident(rev_id, branch_label)
  File "/usr/local/lib/python3.8/site-packages/alembic/script/revision.py", line 546, in _revision_for_ident
    raise ResolutionError(
alembic.script.revision.ResolutionError: No such revision or branch '03f742366750'

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

Traceback (most recent call last):
  File "/usr/local/bin/dispatch", line 8, in <module>
    sys.exit(entrypoint())
  File "/usr/local/lib/python3.8/site-packages/dispatch/cli.py", line 715, in entrypoint
    dispatch_cli()
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1137, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1062, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 763, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/dispatch/cli.py", line 390, in upgrade_database
    alembic_command.upgrade(alembic_cfg, revision, sql=sql, tag=tag)
  File "/usr/local/lib/python3.8/site-packages/alembic/command.py", line 294, in upgrade
    script.run_env()
  File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 490, in run_env
    util.load_python_file(self.dir, "env.py")
  File "/usr/local/lib/python3.8/site-packages/alembic/util/pyfiles.py", line 97, in load_python_file
    module = load_module_py(module_id, path)
  File "/usr/local/lib/python3.8/site-packages/alembic/util/compat.py", line 184, in load_module_py
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/local/lib/python3.8/site-packages/dispatch/database/revisions/core/env.py", line 70, in <module>
    run_migrations_online()
  File "/usr/local/lib/python3.8/site-packages/dispatch/database/revisions/core/env.py", line 64, in run_migrations_online
    context.run_migrations()
  File "<string>", line 8, in run_migrations
  File "/usr/local/lib/python3.8/site-packages/alembic/runtime/environment.py", line 813, in run_migrations
    self.get_context().run_migrations(**kw)
  File "/usr/local/lib/python3.8/site-packages/alembic/runtime/migration.py", line 549, in run_migrations
    for step in self._migrations_fn(heads, self):
  File "/usr/local/lib/python3.8/site-packages/alembic/command.py", line 283, in upgrade
    return script._upgrade_revs(revision, rev)
  File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 366, in _upgrade_revs
    return [
  File "/usr/local/lib/python3.8/contextlib.py", line 131, in __exit__
    self.gen.throw(type, value, traceback)
  File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 203, in _catch_revision_errors
    compat.raise_(util.CommandError(resolution), from_=re)
  File "/usr/local/lib/python3.8/site-packages/alembic/util/compat.py", line 296, in raise_
    raise exception
alembic.util.exc.CommandError: Can't locate revision identified by '03f742366750'
ERROR: 1
Cleaning up...

Thanks for the report I will take a look at this today.

I've updated the example data set here:
https://github.com/Netflix/dispatch/pull/1493
and also slightly modified the install.sh script here:
https://github.com/Netflix/dispatch-docker/pull/113
Currently, our install.sh file points to the latest release, if you want to pick up these changes before we do a release you can modify the install file here:
https://github.com/Netflix/dispatch-docker/blob/master/install.sh#L14
And modify the URL to point to:
https://raw.githubusercontent.com/Netflix/dispatch/master/data/dispatch-sample-data.dump

Thanks @kevgliss for the lightning fast fix!
I wonder if that s in the end of 8f364cf49a23s typo? Because it doesn't match up with 8f364cf49a23

@ymatsiuk ugh you're right let me fix that real quick.

Fixed typo here: https://github.com/Netflix/dispatch/pull/1494

It works now 🎉  Thanks!
PS: Keep in mind that v20210714 is broken, so people who play with dispatch-dockerwill face this issue (it uses latest release by default). Not sure what is the policy around tags you guys have, but you might want to drop this tag. Anyway I'll leave this to you 🙂


Present professional facing services findings to wider NHS Digital community

What
Present the findings of the professional facing services review to the wider community at NHS Digital.
Why
To expose the work that has been done and invite opportunities for feedback and collaboration.
Done when

[ ] Presented at Design Huddle
[ ] Presented at User Research Meetup
[ ] Presented at PD Show & Tell

Slot booked to present at the Design Huddle on Thursday 23rd September and at the UR Meetup on 29th September. Enquired about a slot at the PD Show & Tell and awaiting a response.

Product Development Show and Tell slot booked for 29th September

Presented at the Design Huddle on 23rd Sept, and both the Product Development Show & Tell and User Research meetup on 29th Sept. Had a few people reach out to me around further work that is being done in a professional facing space. I spoke to Cameron Ross about the work being done on the workflow tool and I will update the existing findings with examples from this service.


Unique index with order

$table->unique(['created_at desc', 'post_id']);
Undefined column: 7 ERROR:  column "created_at desc" named in key does not exist

You have to use uniqueIndex instead of unique


[full-ci] chore: bump web to v9.0.0-alpha.5

Bumps Web to v9.0.0-alpha.5.

https://drone.owncloud.com/owncloud/ocis/33755/32/5 sometimes fails
issue for that: https://github.com/owncloud/ocis/issues/8859


Net price calculation does not work with multiple changes if 0% tax rate exists.

To recreate this bug, you must first set a new tax rate with 0% tax in the admin.
Then select products in the product overview and scroll down to the prices. There you enter a gross price, the net price is then not calculated, but the gross price is taken as the net price.
The correct net price is only calculated if you select the standard tax rate as the tax rate in the multiple change. However, this should not normally have any influence on the tax calculation and it makes no sense for 0% to be used as the tax rate for the price calculation if this tax rate is not even stored for the products.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-40004
[created from NEXT-40004, comment 524373]

[public]

Priority changed to: High

Thank you for your report. Based on the information in this report, we have decided to investigate this issue in more detail and are planning to provide a fix for this issue. Although we are always eager to solve such problems as soon as we can, we can't give you a more specific time frame right now. We appreciate your patience and thank you for your understanding.
[created from NEXT-40004, comment 524698]


Add optional additional parameter on save for video to specify "ffmpeg-pass" temporary folder path

Q
A

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Fixed tickets
-

Related issues/PRs
-

License
MIT

What's in this PR?
Add optional additional parameter on save for video to specify "ffmpeg-pass" temporary folder path only for the video processing.
Why?
To specify a temporary folder for saving the written log "ffmpeg-pass" folder to another folder or use the temp folder itself.
Example Usage
$ffmpeg = FFMpeg\FFMpeg::create();
$video = $ffmpeg->open('video.mpg');

// 'tmp/ffmpeg/log' is an additional optional parameter to specify temporary folder path.
$video->save(new FFMpeg\Format\Video\X264(), 'output-video.mp4', 'tmp/ffmpeg/log');

There was a bug in v1.0.0 with the path of the temporary directory. That has been fixed, along with a new configuration setting to customize the temporary directory:
$ffmpeg = FFMpeg\FFMpeg::create(array(
    'temporary_directory' => '/var/ffmpeg-tmp'
), $logger);


Remove some if statements and simplify some boolean expressions

Use QPDFObjectHandle::isNameAndEquals, isDictionaryOfType and
isStreamOfType.

The formatting looks very odd. Any idea why in the vicinity of the changes tabs are expanded to 4 spaces while if one expands the files, in the normally hidden parts of the files tabs are expanded to 8 spaces?

I'll come back to this after I'm done with my current refactoring work. Regarding the formatting, I don't remember seeing github highlight tabs before, so maybe this is new. I'd have to actually pull down the changes and look at them outside of github to be sure.
Your last PR had some weird indentation which I fixed in a separate commit. I guess you are using VS Code. I'm not sure what to do about code formatting. I could start using that ignore-revs thing you mentioned and do one big commit to remove all the tabs. Maybe that would help. (But I would want to do that myself.) I could look into some kind of automatic formatting.
I do all my code editing in emacs and have my "c-style" set to this (referring to myself as "Q" in this context):
(defvar q-cc-style
  '("Q"
    (c-basic-offset . 4)
    (c-comment-only-line-offset . 0)
    (c-offsets-alist
     (defun-block-intro . +)
     (block-open . 0)
     (substatement-open . 0)
     (knr-argdecl-intro . 2)
     (statement-cont . +)
     (case-label . +2)
     (access-label . -2)
     (statement-case-intro . +2)
     (statement-case-open . +2)
     (arglist-intro . +)
     (arglist-close . +)
     (inline-open . 0)
     (inlambda . 0)
    )
  )
  "*cc-mode Style for Q's C++ indentation preference"
)

Most of this dates back to 1997 and has to do with style guidelines that were in place on a project I was working on at the time. It's not how I would do it today. Maybe I need to investigate a batch-mode automatic formatter (like prettier in javascript or go fmt or rust fmt) that would format all my code and just fix it once and for all, as long as I could make emacs get close to it. At this point, my bracing and indentation style has shifted in all my other work, and I do qpdf the way I used to do it only for maintaining consistency in the code base.

clang-format looks very promising. I'm going to add it to my list of things to consider.

Seems as though git blame has a -w option.

I could start using that ignore-revs thing you mentioned and do one big commit to remove all the tabs.

I think that might be good. I looked  into the formatting a bit more after the white-space issues of my last PR. Up to then I used to think that the very odd formatting  I noticed in many part of qpdf was due to the reluctance to unnecessarily touch white space. It turns out that that it is due to VS Code interpreting the files as 4 space indentation, 1 indentation = 4 spaces per tab (same with Genie, the editor that I used until fairly recently). I have managed to persuade both editors to show indentations properly. Unfortunately while doing so, one auto-in/dedents by 8 spaces, and the other uses tabs.I am sure it can be sorted, but removing tabs feels easier.

To be clear, even in the absence of a massive reformatting (which I am now strongly leaning toward), it has been my policy for several years to systematically remove tabs on lines that I change for any other reason. All of our many conversations have convinced me that I put too much emphasis on git blame over convenience and readability though so I am rethinking some things.


+210 xp ?

Bot always captures with +210 xp. if niantic detects it, can it be a way to ban users in future?
any suggestions?

"catch_randomize_reticle_factor" : "0.0"
"catch_randomize_spin_factor" : "0.0"
done.

do i have to add this command to config.json ?

Modify this line and this line in your config
Not an issue with the bot

add to config:
"catch_throw_parameters":{
"excelent_rate": 0.1,
"great_rate": 0.3,
"nice_rate": 0.5,
"spin_success_rate": 0.6
},
and remove
catch_randomize_reticle_factor" : "0.0"
"catch_randomize_spin_factor" : "0.0"

Any update about this?
I tried to change "catch_randomize_reticle_factor" and "catch_randomize_spin_factor" to non-one value, like 0.7 and 0.8, all the pokemons were caught with 210 exp.
I also tried to add
'''
"catch_throw_parameters": {
"excelent_rate": 0.1,
"greate_rate": 0.4,
"nice_rate": 0.6,
"noraml_rate": 0.1,
"spin_success_rate": 0.6
}
'''
The bot is still capturing all with 210 exp.

yes just use this code
"catch_randomize_reticle_factor": 0.1,
"catch_randomize_spin_factor": 0.1,


Pep8

Hello @gustavooquinteiro! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file sample/process.py:

Line 9:36: E251 unexpected spaces around keyword / parameter equals
Line 9:38: E251 unexpected spaces around keyword / parameter equals

In the file tests/test-generator.py:

Line 25:80: E501 line too long (80 > 79 characters)


Fix timeline drawer measurement visualization

Summary
fix #5361
Details and comments
Fix bit link visualization. Currently the drawer tries to visualize the bit link between qreg and creg even though the creg is disabled. This causes an error because the coordinate of the creg is not initialized. In this PR, visible check is moved to correct place so that the link is also disabled. Unittests are also updated.
Box position bug of cregs is not fixed with this PR.

Is there any good way of avoiding this? We can add this warning but current creg output may confuse the users (because measurement on creg always starts from wrong position because creg doesn't have time information).

Is there any good way of avoiding this? We can remove this warning but current creg output may confuse the users (because measurement on creg always starts from wrong position because creg doesn't have time information). Another option is removing debugging stylesheet from docstring, but I want to keep this.

Why is there a warning being emitted into the documentation?

Because in the api docs I showed appearance of timeline images with three different preset stylesheets, namely IQXSimple, IQXStandard, IQXDebugging. Currently show_clbits=True generates a wrong image but IQXDebugging style should show whatever the drawer can according to its stylesheet policy. We should fix this bug at some point but I need more discussion.

I think right now it will be required to remove whatever is causing the warning in the documentation.

close because this is addressed in #5662

close because this is addressed in #5662

close because this is addressed in #5662

close because this is addressed in #5662


build: migrate to pnpm

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/analogjs/analog/blob/main/CONTRIBUTING.md#-commit-message-guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Which package are you modifying?

[ ] vite-angular-plugin
[ ] astro-angular
[ ] create-analog
[ ] router

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

Hi @brandonroberts! I would love to help on the migration to pnpm if this is still something you would like to see getting done.
And is there a reason this pr went stale?

Hi @brandonroberts! I would love to help on the migration to pnpm if this is still something you would like to see getting done.
And is there a reason this pr went stale?

Went to new year party?😁

@Dafnik @t-mish 😂 I definitely would like to finish this migration. I was patching to many things at the time to get it working correctly, and yarn was good enough at the time. The goal is to hook into the Vite Ecosystem CI so we can be checked against upstream
Had a PR there also https://github.com/vitejs/vite-ecosystem-ci/pull/171


Permission Denied error

Hi! This project looks awesome, and I want to try it out.
But I always stuck on Error: EACCES: permission denied, mkdir 'every directory'.
Things I've tried:

Run as root.
Detached volume binding.
Running it on three different systems.
Running both edge and latest.
Defined PUID=1026 (my current user) and PGID=101 (administrative group) on Synology Container Manager.
I can't connect to the container since it was always abruptly closed after permission got denied.

Test systems I've tried:

Synology Container Manager 20.10.23-1437 running on DVA3221.
Docker Desktop 4.26.1 (131620) running on Windows 10.
Docker 20.10.21 running on Ubuntu 22.01.2 LTS VM.

I'm attaching the error log error.
}
Node.js v21.5.0
node:internal/fs/promises:855
  return await PromisePrototypeThen(
         ^
Error: EACCES: permission denied, mkdir '/data/logos'
    at async Object.mkdir (node:internal/fs/promises:855:10)
    at async Promise.all (index 0)
    at async onServerStartup (file:///app/server/chunks/hooks.server-0W6GFEIO.js:67:3)
    at async file:///app/server/chunks/hooks.server-0W6GFEIO.js:81:1 {
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/data/logos'
}
Node.js v21.5.0
node:internal/fs/promises:855
  return await PromisePrototypeThen(
         ^
Error: EACCES: permission denied, mkdir '/data/logos'
    at async Object.mkdir (node:internal/fs/promises:855:10)
    at async Promise.all (index 0)
    at async onServerStartup (file:///app/server/chunks/hooks.server-0W6GFEIO.js:67:3)
    at async file:///app/server/chunks/hooks.server-0W6GFEIO.js:81:1 {
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/data/logos'
}
Node.js v21.5.0
node:internal/fs/promises:855
  return await PromisePrototypeThen(
         ^
Error: EACCES: permission denied, mkdir '/data/logos'
    at async Object.mkdir (node:internal/fs/promises:855:10)
    at async Promise.all (index 0)
    at async onServerStartup (file:///app/server/chunks/hooks.server-0W6GFEIO.js:67:3)
    at async file:///app/server/chunks/hooks.server-0W6GFEIO.js:81:1 {
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/data/logos'
}
Node.js v21.5.0
node:internal/fs/promises:855
  return await PromisePrototypeThen(
         ^
Error: EACCES: permission denied, mkdir '/data/logos'
    at async Object.mkdir (node:internal/fs/promises:855:10)
    at async Promise.all (index 0)
    at async onServerStartup (file:///app/server/chunks/hooks.server-0W6GFEIO.js:67:3)
    at async file:///app/server/chunks/hooks.server-0W6GFEIO.js:81:1 {
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/data/logos'
}
Node.js v21.5.0
node:internal/fs/promises:855
  return await PromisePrototypeThen(
         ^
Error: EACCES: permission denied, mkdir '/data/logos'
    at async Object.mkdir (node:internal/fs/promises:855:10)
    at async Promise.all (index 0)
    at async onServerStartup (file:///app/server/chunks/hooks.server-0W6GFEIO.js:67:3)
    at async file:///app/server/chunks/hooks.server-0W6GFEIO.js:81:1 {
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/data/logos'
}
Node.js v21.5.0
node:internal/fs/promises:855
  return await PromisePrototypeThen(
         ^
Error: EACCES: permission denied, mkdir '/data/logos'
    at async Object.mkdir (node:internal/fs/promises:855:10)
    at async Promise.all (index 0)
    at async onServerStartup (file:///app/server/chunks/hooks.server-0W6GFEIO.js:67:3)
    at async file:///app/server/chunks/hooks.server-0W6GFEIO.js:81:1 {
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/data/logos'
}
Node.js v21.5.0

hi there, i'm sorry to hear that.
I've updated the edge tag (ghcr.io/knrdl/hubleys-dashboard:edge). so when the /data folder is not mounted as a volume (demo mode), it should work again.
The node process in the container runs as PUID=1000. So the volume must have user or group permission set accordingly, e.g. sudo chown -R 1000:1000 ./data.

I can't connect to the container since it was always abruptly closed after permission got denied.

Part of the init procedure is to write to /data. As this fails, the container keeps crashing

Thanks, it's working now.


Show %CPU and %MEM for each node just below IP

When looking at the dashboard and something is strange, I always have to look at the basic machine resources of each machine in order to verify if CPU and MEM are OK. Dashboard could just show this.
Something like:
    server-m1              server-m2
     manager                manager
    <IP_ADDRESS>              <IP_ADDRESS>
  c:10% m:45%       c:97% m:35%

|------------------|------------------|
(with a smaller letter, we can use cpu:10% mem:35% too)
What do you think? I could work on that if needed...

Implemented and merged with https://github.com/mohsenasm/swarm-dashboard/pull/27


Fix vertical-align for add-reaction svg

Before:

After:

Suggestion (also remove unneccesary float and line-height):
.repository .segment.reactions .select-reaction {
  display: flex;
  align-items: center;
  padding: .5rem;
}

.repository .segment.reactions .ui.label {
  padding: .5rem 1rem;
  display: flex;
  align-items: center;
}

.repository .segment.reactions .reaction-count {
  margin-left: .5rem;
}

Before:

After:

@silverwind Feel free to open new PR with your changes, a bit lost about what exactly you want to add, remove or change.

https://github.com/go-gitea/gitea/pull/11496

@CirnoT I don't see any visual differences here

Closed by #11496


workflows: zephyr: remove extra comma from runs-on entry

Comma after board label is causing tests to not be able to find runners.

Pushed this one through


[release-1.11] Upgrade to latest dependencies

release-1.11 http/2 cve -dprotaso
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads
Produced by: knative-extensions/knobots/actions/update-deps

/retest


Fix loader exception on startup when manual server entries are present

There's several ways to fix but clearing the list to remove the designer entry is probably the easiest.

Looks good to me thanks.


Refactor test to remove duplicate definition of ShellCmdResult

This fixes the following error:
/Users/juliandunn/devel/gh/juliandunn/chef/spec/unit/provider/user/solaris_spec.rb:23: warning: already initialized constant ShellCmdResult
/Users/juliandunn/devel/gh/juliandunn/chef/spec/unit/provider/user/dscl_spec.rb:19: warning: previous definition of ShellCmdResult was here

LGTM :+1:

:+1:


Incorrect documentation when using manifest mode with CMake

Firstly, a note that is only a minor issue relating to the documentation not reflecting what appears to be current practice.  Nevertheless, I thought perhaps worthwhile to raise the issue, particularity as this may impact many people's first experience when using Vcpkg under manifest mode with CMake.
The current tutorial on manifest mode explains that for a CMake build the approach is not to run vcpkg install to build and install the dependencies but rather "skip ahead to the next step: Build the project" which installs the dependencies as part of your project's build.  This contradicts the documentation on introducing manifest mode

Manifest mode is engaged by running the vcpkg install command while there's a manifest file (vcpkg.json) in the working directory.

which at least here, is not the case.  Continuing the tutorial, I then observe that the install root for vcpkg_installed is placed in the current build directory and not in the same directory that contains the manifest file.  This likewise contradicts the documentation

Packages installed in manifest mode will not be installed in the global installed directory as they do in classic mode. Instead, each manifest gets its own installation directory named vcpkg_installed; the vcpkg_installed directory is created in the same directory that contains the manifest file.

A consequence is that there is no longer a one-to-one correspondence between your project's manifest file and a unique vcpkg_installed root, since you may have many build directories (debug, release) that each now contain their own vcpkg_installed root.  For example, you may now have
project/
    build/
        debug/
            vcpkg_installed
        release/
            vcpkg_installed
    ..
    vcpkg.json

This matters because all subsequent documentation assumes such a one-to-one correspondence.  This is confirmed in Installation directory layout conventions that explains

In manifest mode, each manifest file has a corresponding vcpkg_installed directory.

which from my understanding is simply not the expected behaviour?
All subsequent documentation then needs some degree of reinterpretation by the reader.  For example, the suggestion to run
vcpkg list

from the directory containing your manifest file can't possibly work - to which install would this refer?
Instead, the approach appears to be something like
vcpkg list --x-install-root build/debug/vcpkg_installed

which works but requires somewhat disregarding the documentation and leaves me wondering if this is in fact correct practice or if I have misunderstood the basic setup of how to use Vcpkg under manifest mode with CMake.
Just finally, some related use-cases using manifest mode with CMake also seem a little light on details, for example when using custom triplets.  If there were an opportunity to update the docs, that might also be worth a look.

Inconsistencies in the documentation are a real problem, and sometimes even show in recommendations given to users here. So your report is useful. But I would like to shift the perspective away from "CMake integration is doing it wrong".
Command line mode is nice if you cannot use buildsystem integration, if you want to issue specific commands, or if you want to pre-fill the artifact cache.
But CMake's capability to have multiple binary dirs and configurations for one source dir makes the single installed tree maintained by the command line a very poor match. Even for the same triplet, installed packages and features can vary, with manifest feature selection via CMake variables. This cannot be reasonably mapped to a single installed tree.

It wasn't my intention to suggest issues with the CMake integration itself, and as it happens (as a long-time CMake user) I'm quite grateful that Vcpkg works well with multiple build trees.  At least from my perspective, finding that vcpkg_installed is placed per build-tree and not as the documentation suggests is a welcome surprise (!).
In fact, in my view this greatly enhances the value of using package manager for dependency management as you can really take advantage of how this automation scales to having multiple triplet combinations (and as you point out, manifest feature variations, too), all locally separated in parallel build-tress.  That combinatorial nature scales poorly when building dependencies manually.
Rather, the emphasis should have been that the documentation doesn't appear to be in sync with such practice. Of course, there's always a chance I had completely misunderstood as the documentation does heavily lean into the single-install-tree approach, almost everywhere (?) outside that first tutorial.  Hence why I thought this worthy of an issue to clarify best practice.  Appreciating how a tool is expected to be used can be very valuable.
I should also have said in my first post, thanks for a great tool!

Thank you for your thorough investigation, detailed analysis, and suggested enhancements. I will update the documents promptly after testing and verifying. If you have any questions, please feel free to let me know. Your contribution is greatly appreciated.

There are two ways to use packages in manifest mode.
When using manifest mode, given C:/vcpkg/, given vcpkg.json, using default triplet x64-windows, taking the build tool CMake and the generator Visual Studio 17 2022 as an example:

For integrated usage

cmake -B build_dir -D CMAKE_TOOLCHAIN_FILE="C:/vcpkg/scripts/buildsystems/vcpkg.cmake"
# packages in ./build_dir/vcpkg_installed
cmake --build build_dir

For non-integrated usage

vcpkg install
cmake -B build_dir -D CMAKE_PREFIX_PATH="vcpkg_installed/x64-windows"
# packages in ./vcpkg_installed
cmake --build build_dir

Issues related to the documents of vcpkg now need to be reported at https://github.com/microsoft/vcpkg-docs. I have moved it for you, the new issue is https://github.com/microsoft/vcpkg-docs/issues/349.

For non-integrated usage

vcpkg install
cmake -B build_dir -D CMAKE_PREFIX_PATH="vcpkg_installed/x64-windows"
# packages in ./vcpkg_installed
cmake --build build_dir

This is nearly unusable, because it doesn't use any vcpkg-cmake-wrapper.cmake.


This is pre-commit hook that will prevent you from committing this type of content. It could be extended later on.
There are NPM packages Git Hook packages that could do the same thing, but right now I don't think that there is a big need for that.
In the rare case that you will need to commit change that include fdescribe or some of the other words. This could be done with:
$ git commit -m "fix: skip few tests from running " -s -S --no-verify

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

TSLint will prevent the debugger keyword and there is also TSLint rules for Jasmine https://github.com/kaiza/tslint-jasmine-rules While these wont catch at time of commit they would catch at build time and prevent it from being merged.

Yes, we shouldn't duplicate what TSLint does by writing more scripts. I've also avoided adding linting to commit hooks because it can be a bit frustrating at times when you're doing a lot of exploratory work.

I'm ok with this checks, but don't see the reason that this has to be committed and tested on the remote side when it could be prevented and save time waiting for the build to fail.
Also, I'm thinking that a check for <<<<<<<, >>>>>>> and =======. So non umerged files could be commited.

I'm going to close this as something we don't want right now. You might be able to commit merge conflicts, but it won't build so will get flagged on Travis. If you want to run the checks locally you certainly can.


detect mixed spaces/tabs or missing parameters

In this case the normal map just silently failed to draw, but the rest of the map did. Not sure how extensive the current internal linting is or if there's any kind of error which could be thrown in this case...

Tabs are technically forbidden in YAML, and Tangram's internal YAML parser has not resolved this since the issue was opened in 2013, even after the YAML spec creator weighed in: https://github.com/nodeca/js-yaml/issues/80
The summary is that we have to catch these errors ourselves or do the work of patching js-yaml upstream.
Incidentally, I have considered writing functionality in Tangram Play that can highlight these as errors, or convert them for you. We already insert spaces instead of a tab character when you press tab, so there's no chance of accidentally inserting tabs when authoring in Play.

Illuminating: https://github.com/nodeca/js-yaml/issues/80#issuecomment-158592334 – would it be worth considering libyaml at this point?

Libyaml is python, I believe...? Is there a direct JS port?
On Tue, Jun 21, 2016, 10:43 AM Peter Richardson<EMAIL_ADDRESS>wrote:

Illuminating: nodeca/js-yaml#80 (comment)
https://github.com/nodeca/js-yaml/issues/80#issuecomment-158592334 –
would it be worth considering libyaml at this point?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tangrams/tangram/issues/338#issuecomment-227461983,
or mute the thread
https://github.com/notifications/unsubscribe/ACb1tK5F03u-LDBqDrsa0mXFlteLc3XJks5qN_iFgaJpZM4I6Rd3
.

Ah, missed that. Not to my knowledge.

LibYAML is a C library, with bindings to many languages. It could probably be transpiled to JS with emscripten but I'm not aware that this has been done already. LibYAML also has a SAX-style parsing interface, which deterred us from using it in tangram-es.

From the research I've done, I believe js-yaml is far and away the best JS YAML library.

Let's patch it!![](https://link.nylas.com/open/c3ccrw0t3xj00dylcqc5uc6ma
/local-
0c7eff53-ac75?r=cmVwbHkrMDAyNmY1YjRjYmNmNjQ2OTIxNmZhZjkzNzA0ZmU0OTdjODUxNGU4M2U3YzQ3Y2JiOTJjZjAwMDAwMDAxMTM4MTFiZDk5MmExNjljZTA5OWRhZmYyQHJlcGx5LmdpdGh1Yi5jb20=)
On Jun 21 2016, at 11:14 am, Brett Camper<EMAIL_ADDRESS>wrote:

From the research I've done, I believe js-yaml is far and away the best JS
YAML library.

—
You are receiving this because you commented.
Reply to this email directly, view it on
GitHub,
or mute the
thread.

Closing with WONTFIX as out of scope.


Dashboard: rework design of index file

Personally this does not look professional at all. It looks like boilerplate vuejs code / styling.
Can we drop the text above the button and make the button another color with maybe a login icon inside?
Look at something in here: https://dribbble.com/search/shots/popular/web-design?q=call to action

Welcome to 3Bot
Click the button below to access your 3Bot Admin Panel via 3Bot Connect Authorization
Log in via 3Bot Connect

this page should be deleted. instead, change the text of the existing authorization page so there should be no duplication
https://github.com/threefoldtech/js-sdk/issues/903

that's my temporary fix (i'll keep that issue in the backlog to improve)
fedc359748ba20e2a359c7dc11f1da5e9c870176

this page should be deleted. instead, change the text of the existing authorization page so there should be no duplication
#903

this page has nothing to do with "login page", login page is a generic page used for ALL packages requiring login, admin panel happens to be one of these package.

@xmonader looks better already!


Correctly detect the target directory

The only way cargo provides to get the target directory, is to use cargo metadata.
Requiring that we get a directory at the project root adds additional clutter.
For reference, I'm want this for vello, which uses run-wasm for examples, and therefore puts it in the examples directory.
This should also ensure that we obey the wishes of any users who wish to use a global target directory.

I have now tested this in vello on windows, and it works as expected.

Thankyou for raising this, generating an extra target directory is a genuine issue.
Unfortunately cargo metadata is really expensive! I measured 300ms against vello on the laptop im currently using.
I wonder if we could use the current method and then fallback to a more robust method if the target directory is missing?
Maybe it would be enough to traverse up the directory tree until we find the outermost Cargo.toml.
Or maybe we really do need to call cargo metadata
Additionally if we do use the cargo metadata solution we should process a serde_json::Value instead of introducing the serde_derive proc macro as that will affect overall build times as the proc macro needs to finish compiling before cargo-run-wasm can start compiling.

To clarify, when you checked cargo metadata, I'm presuming that was with --no-deps set?
It is very frustrating that cargo doesn't provide a way to just get this value directly.
The shortcut of checking one level up the directory tree is a good idea, I'll implement that.

Oh I'll have to try --no-deps, sorry I missed that

I can confirm --no-deps is significantly better: ~80ms
Its still not ideal though, so a shortcut would be appreciated.

I've now implemented the shortcut, which should execute concurrently with cargo metadata - the shortcut has priority to ensure that we get a consistent result, even though it might sometimes be wrong.

I've now tested with wgpu, winit and vello; all three of which now work correctly.


 Here are a couple of improvements we can make:

Create a separate job for 1, 2, and 3.
pytest is already ran serially on different subset of test, we could try to parallelize this via a matrix strategy. This is related to #639.
https://github.com/google/flax/blob/605785513c5c495b7254882c8a09bf7ac4649fd8/tests/run_all_tests.sh#L53-L55

Notes

I don't know if its intended but run_all_tests.sh also runs doctest, we should consider removing it from here.

https://github.com/google/flax/blob/605785513c5c495b7254882c8a09bf7ac4649fd8/tests/run_all_tests.sh#L43

Right now we only test with python 3.7, should we consider testing on more versions?

Solved by #2458 which created a matrix that splits up tests into doctest, pytest, and pytype.


Removed run_forseti.sh shell script from Forseti repository

Resolves part of #3313
Removed run_forseti.sh shell script from Forseti repository in an effort to migrate deployment scripts to Terraform Google Forseti repository.
#457 has been opened to move run_forseti.sh to Terraform Google Forseti repository.

[x] I signed Google's Contributor License Agreement
[x] My code conforms to Google's python style.
[x] My PR at a minimum doesn't decrease unit-test coverage (if applicable).
[x] All of the tests pass.

Merge this in when this PR is merged.


Declare the overall language of a page in the html root tag instead of using the meta tag

This moves the declaration of the language to the top / root  tag and both pages become HTML5 compliant.
See https://www.w3.org/International/techniques/authoring-html.en?open=language&open=textprocessing#textprocessing for more details.

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

Thanks for your contribution, can you apply that change to the frontend of the API api/frontend/main.php as well?


[Bug/Feature]: Latex math does not show up properly with bibtex

Debug log ID
ERRT3373-refs-euc
What happened?
Latex math enclosed in $$ (for example in titles) does not show up properly.
For example, the exported .bib for the reference in the debug log is
@article{zacheDynamicalTopologicalTransitions2019,
  title = {Dynamical {{Topological Transitions}} in the {{Massive Schwinger Model}} with a \$\textbackslash ensuremath\{\textbackslash theta\}\$ {{Term}}},
  author = {Zache, T. V. and Mueller, N. and Schneider, J. T. and Jendrzejewski, F. and Berges, J. and Hauke, P.},
  year = {2019},
  month = feb,
  journal = {Phys. Rev. Lett.},
  volume = {122},
  number = {5},
  pages = {050403},
  publisher = {{American Physical Society}},
  doi = {10.1103/PhysRevLett.122.050403},
  urldate = {2022-06-24},
}

which does not show up properly in the latex generated document (using bibtex + revtex4.2). The title shows up with $\ensuremath{\theta}$. Instead of the actual symbol for \theta.
Replacing the title field with   title = {Dynamical {{Topological Transitions}} in the {{Massive Schwinger Model}} with a $\ensuremath{\theta}$ {{Term}}},
makes it show up properly.

Zotero has no latex math support, so a dollar sign is just a dollar sign in Zotero, but you can make BBT recognize math section:
https://retorque.re/zotero-better-bibtex/exporting/scripting/#detect-and-protect-latex-math-formulas

That works. Thanks!


Face method 'bounding-box' should return a four-element array or list as in Font::AFM

Similar to Font::AFM's FontBBox.

I'm relucent to change bounding-box given that it's already in use.
Instead, I'm  adding a FontBBox method that returns an array.  Also adding documentation that bounding-box returns a struct with x-min, y-min, x-max and y-max accessors.
Hope this suits.

That's fine, David. Thanks!


Unable to turn on guard mode

First off, this amazing!  I have done so much with it right away.  I was looking at adding a trigger to enable Guard Mode however under alarm_control_panel.alarm_arm_home is alarm_control_panel.home_alarm, i dont see another entity tied to amazon to trigger that?  Or am I missing something?  I have v 1.3.0 installed.  I have guard mode enabled in my alexa app and it's working fun.

As I just release 1.3.0 about 10 minutes ago, I'm not sure if you actually had it installed.  Please verify you're on 1.3.0 and if you're still seeing issue provide some logs from alexapy
I'll close this for now, but please reopen if it persists.

Gosh I feel like a heel, thanks, you're right, I didnt realize I didnt have 1.3.0, I just updated and it's there now as an entity.

No biggie, I teased it on the forum when I had it staged and you're not the only one who thought I meant I had released it.


Move to node10

I also tested this locally and all looks fine.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM.


OBM driver for IPMI 1.x

@gsilvis, @henn and I just had an in-person dicsussion re: supporting IPMI 1.x (prompted by the comments in #457). We're going to go ahead with dropping support in the core for now, but once the OBMs have been drivertized, we may want to add this functionality back in. This is still TDB; for the record I'm against it, but we're deferring the discussion and recording it in this issues.

do we really need to support ancient hardware at this point? I remember upgrading the sun machines' IPMI to work with our current driver (see #694)

I was against the idea when this issue was opened, and yeah, I think it's still not worth it, and we should close this. @henn, how do you feel about this these days?

@henn hasn't responded; I am closing this issue for now. Reopen it if you think this is pertinent.


Error when trying to publish mesh application, "Unable to edit or replace'test': previous deployment is still active"

I'm attempting to use Service Fabric Mesh to deploy a container based app. I'm new to Mesh, but I did get the sample 'Hello App' working. Now I'm trying to deploy an app based on a container I have stored in Azure. I used the following command to deploy this:
az mesh deployment create --resource-group MikeMesh --template-file test.json
The command says 'Deploying . . .' for about 10 minutes, and then says:
Unable to edit or replace deployment 'test': previous deployment from '8/20/2018 9:55:28 PM' is still active (expiration time is '8/27/2018 9:55:27 PM'). Please see https://aka.ms/arm-deploy for usage details.
Note this is a brand new resource group, and I've never deployed anything here before.  Also note I can deploy this same container using normal Service Fabric and it works fine.
The link in the error message doesn't contain anything helpful. If I go to the 'Deployments' tab, the status says 'Deploying' but it seems stuck (it's been nearly two hours). If I click on 'Related events', I get 3 events but all of them say 'Succeeded' or 'Accepted'. Under 'Quick Insights' if I click 'Failed deployments', I see a 'Validate deployment' operation that failed 2 hours ago, but I'm not clear if this has anything to do with this deployment. The error message for that is the same as what I saw on the command line.
The test.json is as follows (with some sensitive information removed):
{
  "$schema": "http://schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json",
  "contentVersion": "<IP_ADDRESS>",
  "resources": [
    {
      "apiVersion": "2018-07-01-preview",
      "name": "LimeadeMeshNetwork",
      "type": "Microsoft.ServiceFabricMesh/networks",
      "location": "eastus",
      "dependsOn": [],
      "properties": {
        "addressPrefix": "<IP_ADDRESS>/22",
        "ingressConfig": {
          "layer4": [
            {
              "publicPort": "80",
              "applicationName": "LimeadeApp",
              "serviceName": "WebsiteService",
              "endpointName": "WebsiteListener"
            }
          ]
        }
      }
    },
    {
      "apiVersion": "2018-07-01-preview",
      "name": "LimeadeApp",
      "type": "Microsoft.ServiceFabricMesh/applications",
      "location": "eastus",
      "dependsOn": [
        "Microsoft.ServiceFabricMesh/networks/LimeadeMeshNetwork"
      ],
      "properties": {
        "description": "Limeade Mesh Application",
        "services": [
          {
            "type": "Microsoft.ServiceFabricMesh/services",
            "location": "eastus",
            "name": "WebsiteService",
            "properties": {
              "description": "Limeade Website Service",
              "osType": "windows",
              "codePackages": [
                {
                  "name": "WebsiteCode",
                  "image": "web:20180720103109",
                  "imageRegistryCredential": {
                    "server": "<container>.azurecr.io",
                    "username": "<username>",
                    "password": "<password>"
                  },
                  "endpoints": [
                    {
                      "name": "WebsiteListener",
                      "port": "80"
                    }
                  ],
                  "resources": {
                    "requests": {
                      "cpu": "1",
                      "memoryInGB": "1"
                    }
                  }
                }
              ],
              "replicaCount": "1",
              "networkRefs": [
                {
                  "name": "[resourceId('Microsoft.ServiceFabricMesh/networks', 'LimeadeMeshNetwork')]"
                }
              ]
            }
          }
        ]
      }
    }
  ]
}

More info

Referencing @MicahMcKittrick-MSFT

@BharatNarasimman would you be able to help get someone to assist @MikeChristensen?
I worked with him on a doc related question #13830 but I was not seeing the same behavior so think he should work directly with all of you to get it sorted out in case it is an issue with Mesh itself.

@vaishnavk

Tried this again on Oct 18 - Still having same issue.  Anyone want to help with this?

Can you try using the -n flag for the az mesh deployment create command, to see if you still have conflicts with existing deployments?

Is -n the same as --name?  If so, I'm already using that parameter.  I've tried deploying into two resource groups, both are brand new and have never had any deployments, so nothing to conflict with.  The first deployment finally finished after 2 hours and 21 seconds, and gives me the error:
{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
  "details": [
    {
      "code": "RequestTimeout",
      "message": "{\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource provision operation did not complete within the allowed timeout period. Please see https://aka.ms/arm-deploy for usage details.\"\r\n  }\r\n}"
    }
  ]
}

The second deployment is still in progress (it's been about an hour and a half).  I cannot find any information as to what exactly it's doing or where it's getting stuck.  Let me know if you want any other logs or info.

Do you mean Mesh deployments?  Or Service Fabric deployments?  Or any sort of deployments of any sort?
Also, I can use a GUID for my deployment name if that would help.

Any deployments that are still running that share that name over all your resource groups on that subscription.  a GUID should help with avoiding name conflicts.

I doubt there's any deployment with that same name.  I'll try again and use a GUID.

Running with command:
az mesh deployment create --resource-group MikeMeshTest --name 52d74104a43d40f691bc56400085716e --template-file .\test.json

I get this same error every time I try to use az mesh deployment create to scale up one of my containers from 1 replica to 3 (based on the steps shown in the tutorial here). The command takes 10 minutes or so to time out and reports
Unable to edit or replace deployment 'sfmesh-example-voting-app': previous deployment from '10/23/2018 1:40:18 PM' is still active (expiration time is '10/30/2018 1:40:02 PM'). Please see https://aka.ms/arm-deploy for usage details.

The "previous" deployment appears to be referring to the first deployment where I created the app in the first place which already completed successfully. az deployment list returns nothing.
Strangely, while the deployment is in progress I do see (from the portal) that the target service scales out to 3 replicas and I can see that I can communicate with at least 2 different replicas. However, after az mesh deployment create fails,  even though az mesh service list shows 3 replicas for that service, but I can see both from the portal and my own app responses that there is now only 1 replica running again.
Not sure what else to try - this is happening every time, and with a few different test applications.

Yea I'm starting to think this is a generic error that hides some real error that's going on underneath.  I think the first thing they need to fix is their error handling, so we can see what's actually going on.

OK, I've managed to narrow my issue down further. I get the timeout if I have >1 replica of a service with an endpoint. Scaling out services without endpoints to multiple replicas does appear to work, although the az mesh deployment create command still hangs indefinitely.

There is a bug that was causing the error "unable to edit previous deployment", there is a fix being worked on. But that error does not actually stop the deployment, you can also use this command for the same effect https://docs.microsoft.com/en-us/cli/azure/group/deployment?view=azure-cli-latest#az-group-deployment-create it wont check for IP addresses of the mesh applications though.
As for your last issue, @mattrowmsft would you know what could be going wrong with the container failing

I am facing same issue when I am trying to deploy the Linux container. When I use az mesh app show, it shows 'There was an error during CodePackage activation.Service host failed to activate. Error:E_FAIL'\r\n".


Legacy and Outback port

Can you do the panda PR on the panda repo?

It's riccardo's already open PR

Yes, I'll fix the conflicts and merge:
https://github.com/commaai/panda/pull/189

That close/delete was accidental

75 up and down are the limit the EPS seem to follow. I'll change this to follow impreza.

I have a Subaru Forester 2018 Premium I'd like to try and get working with this as well.

Follow-up master based PR is here https://github.com/commaai/openpilot/pull/1489


ARROW-11735: [R] Allow Parquet and Arrow Dataset to be optional components

Not implemented for Windows yet (that's ARROW-11884)

Oh, one other thing: in inst/build_arrow_static/sh, you'll want to make ARROW_PARQUET and ARROW_DATASET configurable by env var but default ON, just like ARROW_JEMALLOC. That way, we can make a CI job that sets them to OFF in the env so we can test this.

Oh, one other thing: in inst/build_arrow_static/sh, you'll want to make ARROW_PARQUET and ARROW_DATASET configurable by env var but default ON, just like ARROW_JEMALLOC. That way, we can make a CI job that sets them to OFF in the env so we can test this.

Done in 8c5b235dddac47833b229323b4a216049eae5fea

@github-actions crossbow submit -g r

@github-actions crossbow submit test-r-minimal-build

@nealrichardson do you want LIBARROW_MINIMAL to toggle Dataset and Parquet? I assume no.

@nealrichardson do you want LIBARROW_MINIMAL to toggle Dataset and Parquet? I assume no.

Correct, we don't want to change that meaning (yet).

@github-actions crossbow submit test-r-minimal-build

@github-actions crossbow submit test-r-minimal-build

@github-actions crossbow submit test-r-minimal-build

@github-actions crossbow submit test-r-minimal-build

@github-actions crossbow submit -g r

@github-actions crossbow submit test-r-minimal-build

@github-actions crossbow submit -g r

@github-actions crossbow submit test-r-without-dataset-parquet-s3

The environment variables are being set in the container now, and Arrow is building with Dataset and Parquet off, but S3 is remaining on despite the environment variable.

S3 is on because linuxlibs.R is turning it on: https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=1741&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=6c939d89-0d1a-51f2-8b30-091a7a82e98c&l=24
I think you'll find the issue pretty quickly but LMK if you need a pointer.

@github-actions crossbow submit -g r

Good catch about the Windows builds. Could you make followup JIRAs for:

configure.win should determine Arrow C++ library capabilities dynamically (like we do in configure)
LIBARROW_MINIMAL=true should entail that all optional features are OFF

configure.win should determine Arrow C++ library capabilities dynamically (like we do in configure)

ARROW-11884

LIBARROW_MINIMAL=true should entail that all optional features are OFF

ARROW-11885

Sorry, I just merged the dataset mutate() PR which added a cpp function. Can you please rebase and update the annotation on that function? Otherwise this is looking good, will merge.

Sorry, I just merged the dataset mutate() PR which added a cpp function. Can you please rebase and update the annotation on that function? Otherwise this is looking good, will merge.

Done

@github-actions crossbow submit test-r-minimal-build

@github-actions crossbow submit test-r-minimal-build

@github-actions crossbow submit test-r-rstudio* test-r-minimal-build


fixed file name for conversion response module

Fix for issue https://github.com/singnet/snet-converter-services/issues/112

Issue https://github.com/singnet/snet-converter-services/issues/112 was closed.


wire mimir into REPL

Closes #2218

@alissapajer Build failures seem to be because we now have multiple versions of Spire on the classpath?  I think this is because both SSTs and Mimir use Spire.  We should fix that.

@djspiewak back in your court.

@djspiewak assembly settings are fixed.


Documentation is unclear on how to cancel a websocket handshake

Given:
ws is an object of a type which is a specialisation of boost::beast::websocket::stream<>
Scenario:
ws.async_handshake(...) is in progress.
and
Client program wishes to terminate while being a good citizen.
Should the client program:
a) simply cancel() the underlying socket and exit?
b) wait for the async_handshake to complete, remembering the intent to close the connection and then issue ws.async_close()?
c) issue ws.async_close() during the handshake?

The only thing you can do is cancel the underlying socket. async_close does not work before the handshake is complete.

The only thing you can do is cancel the underlying socket. async_close does not work before the handshake is complete.

But doing so would prevent a clean shutdown of the ssl layer, or would it ?

But doing so would prevent a clean shutdown of the ssl layer, or would it ?

Canceling the handshake operation leaves the stream in an undefined state, which is why only terminal cancellation is allowed. A clean SSL shutdown requires coordination between both sides, but that is no longer possible on this stream.

But doing so would prevent a clean shutdown of the ssl layer, or would it ?

Canceling the handshake operation leaves the stream in an undefined state, which is why only terminal cancellation is allowed. A clean SSL shutdown requires coordination between both sides, but that is no longer possible on this stream.

That's what I thought.
So basically it's not possible to cancel a wss handshake at all, all we can do is close everything and instantiate another stream ?
I've been trying to find out how the appropriate sequence of asyncronous call for closing the connection on whatever state it is in, and the documentation is lacky to say the least.
here are the different cases to cover:

the stream is connecting to tcp
in this case, it seems to be fine just canceling the tcp layer (didn't crash at least)
the stream is connecting to ssl
the stream is connecting to ws

It's a bit off the topic of this thread but I was curious to know exactly how to handle disconnection of wss stream.
there are several configurations to take care of:

the stream is connecting to tcp : apparently it's ok to just cancel that layer
the stream is connected to tcp : same thing
the stream is connecting to ssl : based on my tests trying to close ssl will crash, and the assertion is clear that
I should not make a call while it's connecting, so once again we are left with cancelling the tcp layer I suppose.
the stream is connected to ssl : now we can gracefully close the full ssl stack via the ssl layer
the stream is connecting to wss : now we can't, again assertions fire. but now we have a ssl session open which we
can't close properly unless we wait for the outstanding wss handshake to be done.
the stream is connected to wss : now we can close, but only when no i/o operation is outstanding, so we need to
cancel them first and then async_close the wss stack. but in practise the per-op cancellation was taking ages so the only practical way to cancel i/o was to cancel the tcp layer.

So in the end I gave up on all that undocumented complexity and I decided that just cancelling tcp was working for all cases.
I was concerned with security but it seems to be just fine since the connection is entierly dropped anyway, and obviously the applicative protocol should be designed to always await confirmation for transactions.
Am I correct ?


Will you update this tools and is there a way to speed it up?

Hi I was just wondering will you update this tool and is there a way to speed it up.
It is a really good tools just wish it was faster.

Exactly!

We all hoping for an update!


refactor(connector): [Rapyd] Currency Unit Conversion

Type of Change

[x] Refactoring

Description

Closes https://github.com/juspay/hyperswitch/issues/2244
Motivation and Context

Hacktoberfest
How did you test it?

Could not test as this was not updated and the postman collection does not exist for Rapyd:

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code

Closing this!


Using around_action to set the locale

Why
To set the locale in before_action, there will is a case that the I18n can't get the default locale for some request, I faced that in a project.
For more details:

https://github.com/ruby-i18n/i18n/issues/381
https://github.com/rails/rails/issues/34043
https://github.com/rails/rails/pull/34356
https://guides.rubyonrails.org/i18n.html#managing-the-locale-across-requests

Solution
I think we should go with the Rails way, using around_action instead - https://guides.rubyonrails.org/i18n.html#managing-the-locale-across-requests

@andyduong1920 do you have more information about this case? What was the problem? In which situation was the local not assigned properly? (maybe in an Engine controller that did not inherit from the main ::ApplicationController? 🤔 )
My case is that around_action is resetting the locale to the default value after the action, and this is bad with Devise flash messages when login fails: because devise redirects to the login page, and sets the flash message after the action is completed, so the locale value used will be the default one, not the current one =/
Thanks for your lights! 🙌

That is the case @malparty we set the locale on before_action, but the flash message didn't get localized.


Doesn't explain non-gateway scenario, doesn't explain how to add schedule times

The Gateway connection and Data source credentials sections should explain the scenario where the dataset does not require a gateway e.g. reading from SharePoint Online or OneDrive. Currently it's implied that some kind of gateway is mandatory.
Also the Schedule refresh section does not describe the steps need to add refresh times and the limitation of 8 times per day for Free & Pro workspaces.

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

ID: 5a72e523-2194-f53c-9a27-abf960e77851
Version Independent ID: bdc43737-adc5-b7bf-245e-e065a1478566
Content: Configure scheduled refresh - Power BI
Content Source: powerbi-docs/refresh-scheduled-refresh.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @Mike-Honey . We’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

@Mike-Honey - Thanks MIke for the feedback. I think for the first one, We already mention that we require gateway only to connect to On-premises sources.
Agree about the second feedback.
@mblythe

I second this issue. Still unclear whether a source such as Azure PostgresDB requires a gateway or not and, if it does not, how to configure it.

@arthiriyer - will address this as part of gateway docs update

We now have a centralized data source article - https://docs.microsoft.com/en-us/power-bi/power-bi-data-sources. Let us know of any additional feedback there. Thanks!


Cannot listen open to the port on Chrome

Tony,
Following your tutorial I've ran into an error for some reason I cannot seem to get the webpage to open to the port specified on the main.py (which was 5000 by default)
The odd thing is that I can open up to http://raspberrypi:5000/ using Midori on the raspberry pi but not on my Mac. I've tried to change the port to 8000 to see is this port issue could be resolved but it is not woking any pointers to solve the problem would be great.
Here's the code used:
`from flask import Flask
app = Flask(name)
@app.route("/")
def hello():
return "Hello World!"
if name == "main":
app.run(host='<IP_ADDRESS>', debug= True)`
-Nemesis

To try solve this, I would check what the IP address of your RaspberryPi is  and use that in the URL i.e.
http://<IP_ADDRESS>:5000/


Agregore protocols

Adds custom protocol handlers to agregore.

Gonna close this since it's way out of date


Make assert location transaction page look nice

Fixes #121
Adds the following improvements to the assert location transaction view:

has its own file now (instead of using the fallback JSON dump)
shows a map with a marker for the new asserted location
shows fees in correct denomination
shows who paid the staking fee (staking server or hotspot owner)
shows location nicely formatted, e.g.: "City, State, Country" as long as the hotspot's current lat/lng matches the one asserted in the transaction

@madninja for the last item above ^, would it be easy / feasible to add the geocode data to the assert location transaction response? Right now I have the page doing an extra client-side fetch for the hotspot data, and using the geocode given given for the hotspot to display City, State, Country names so you don't have to zoom out on the map to know where the assert happened. But obviously that method won't work when the hotspot's current location is different from the one that was asserted in that transaction.
Also added a color tag for add_gateway_v1 and assert_location_v1 transactions:

You can see them here:
http://helium-explorer-pr-136.herokuapp.com/accounts/14fzfjFcHpDR1rTH8BNPvSi5dKBbgxaDnmsVPbCjuq9ENjpZbxh
Screenshots:
This page before:

https://explorer.helium.com/txns/rzZc7rLqqGlMwoHPquu7RQ3fSnCuZlVI85wOJvNrQTo
This page in this PR:

https://helium-explorer-pr-136.herokuapp.com/txns/rzZc7rLqqGlMwoHPquu7RQ3fSnCuZlVI85wOJvNrQTo

this looks good, certainly a big improvement over the current state. I left comments in the http issue, but think we should add geocode to the transaction response rather than querying a general purpose api

No other data is pushed into specific transactions today, why would we break this now?

this looks good, certainly a big improvement over the current state. I left comments in the http issue, but think we should add geocode to the transaction response rather than querying a general purpose api

No other data is pushed into specific transactions today, why would we break this now?


Implement a Web-Based Text Editor

Objective:
Implement a web-based text editor using a modern JavaScript library (such as CodeMirror or ACE Editor) integrated into the existing Flask application.
Description:

Route Setup: Add a new route /editor in main.py to handle the editor functionality.
Frontend Integration: Create a front-end template (editor.html) to utilize a web-based code editor for editing and saving file content.
Editor Features: Include features like syntax highlighting, line numbers, and basic editing capabilities.
File Handling: Enable users to open, edit, and save files directly from the web interface.

Steps:

Update main.py: Add a new route to process GET and POST requests for the editor.
Create editor.html: Use CodeMirror (or ACE Editor) embedded in an HTML form for the front-end editor interface.
Form Handling: Manage file content updates and save changes when the form is submitted.

Example Code:
main.py
@app.route('/editor', methods=['GET', 'POST'])
@flask_login.login_required
def editor():
    if request.method == 'POST':
        file_content = request.form['file_content']
        with open('path/to/your/file.txt', 'w') as f:
            f.write(file_content)
        return redirect(url_for('editor'))  # Redirect to the editor after saving
    with open('path/to/your/file.txt', 'r') as f:
        file_content = f.read()
    return render_template('editor.html', file_content=file_content)

editor.html
<!DOCTYPE html>
<html>
<head>
    <title>Text Editor</title>
    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/codemirror/5.65.5/codemirror.min.css">
    <script src="https://cdnjs.cloudflare.com/ajax/libs/codemirror/5.65.5/codemirror.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/codemirror/5.65.5/mode/python/python.min.js"></script>
</head>
<body>
    <form method="POST">
        <textarea id="code-editor" name="file_content">{{ file_content }}</textarea>
        <button type="submit">Save</button>
    </form>
    <script>
        var editor = CodeMirror.fromTextArea(document.getElementById('code-editor'), {
            lineNumbers: true,
            mode: 'python',
            theme: 'default'
        });
    </script>
</body>
</html>

Ensure the feature is fully functional and tested before deployment.

Likely this is implemented in the shell.


how to write Topology for kafka

Hi guys,
When I write a Topology for kafka , I got an error when build:
pyleus build: error: [VirtualenvError] Failed to execute Python module: kafka_spout_example.msg_print. Error: /tmp/tmpllh9zN/resources/pyleus_venv/bin/python: No module named kafka_spout_example
it seems bolt module can not be found , however , I create my directory:

kafka_spout_example

pyleus_topology.yaml
kafka_spout_example

msg_print.py

My topology:

name: kafka_spout_example
topology:
- spout:
    name: kafka-my_topic
    type: kafka
    options:
        # The Kafka topic to stream from.
        # Required.
        topic: my-replicated-topic5

        # ZooKeeper connection string. Comma-separated list of ZooKeeper
        # servers.
        # Required.
        zk_hosts: localhost:2181

        # Root path in ZooKeeper to store consumer offsets.
        # Defaults to: /pyleus-kafka-offsets/<topology name>
        zk_root: /pyleus-kafka-offsets/kafka_spout_example

        # Kafka consumer ID.
        # Defaults to: pyleus-<topology name>
        consumer_id: pyleus-kafka_spout_example

        # Whether the initial offset should be that specified by
        # start_offset_time (true) or the head of the stream (false).
        # Defaults to false.
        from_start: false

        # The offset time to start with if from_start is true.
        # Defaults to the earliest offset time in the stream.
        start_offset_time:<PHONE_NUMBER>
- bolt:
    name: kafka_msg_print
    module: kafka_spout_example.msg_print
    parallelism_hint: 1
    groupings:
        - shuffle_grouping: kafka-my_topic

Hi @zhaohanqing,
I think your problem is that you are missing an empty file named "init.py" in your inner kafka_spout_example folder. That file makes it a python module. Just create it and you should be set.

Hi @jswetzen , you are right , after add init.py it worked .
Thank you very much !


Convert Dlib from Docbook to CommonMark

This issue tracks the conversion of /doc/builders/packages/dlib.xml from Docbook to CommonMark per RFC 72.
If you intend to work on this conversion, please comment below!
Conversion instructions

Comment here that you intend to work on it. (Please also post if you stop working on it.)
Checkout a new branch of nixpkgs master.
Edit doc/builders/packages/index.xml: change dlib.xml to dlib.section.xml.
Rename doc/builders/packages/dlib.xml to dlib.section.md.
Convert the contents from Docbook to CommonMark. Follow conversion best practices. Use existing .md sections for inspiration.
Use nix-build from the doc/ folder to build the manual.
Preview the manual on your computer at http://<IP_ADDRESS>:8000/manual.html after running from doc/ folder:

nix-shell -p python3 --run 'python3 -m http.server --directory ./result/share/doc/nixpkgs'

When it looks good, submit a PR and reference this issue.

Hi @ryantm,
Opened PR #108919 for this.

Hi @ryantm,
Opened PR #108919 for this.


[Consolidated KafkaChannel] [WIP] Set KafkaChannel consolidated dispatcher OwenrRef

Proposed Changes

Set the consolidated KafkaChannel controller deployment as the owner of the dispatcher deployment. This means that the way to uninstall the KafkaChannes is by deleting the controller deployment only.

Release Note

- 🧽 The consolidated KafkaChannel dispatcher is now owned by the controller.

/retest

@devguyio
You need to delete this sym-link https://github.com/devguyio/eventing-kafka/blob/srvke-910/config/channel/consolidated/500-dispatcher.yaml

Works... see ownerReferences
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
  creationTimestamp: "2021-08-10T11:18:02Z"
  generation: 1
  name: kafka-ch-dispatcher
  namespace: knative-eventing
  ownerReferences:
  - apiVersion: apps/v1
    controller: true
    kind: Deployment
    name: kafka-ch-controller
    uid: 738f6cb0-dd46-4fd9-856f-341bb35c4737

and therefore the clean up works...

/retest

/test pull-knative-sandbox-eventing-kafka-upgrade-tests

Aug 11 00:00:28.591 install_head_consolidated_channel [OUT] The Deployment "kafka-ch-controller" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/component":"controller", "app.kubernetes.io/name":"eventing-kafka-channel", "messaging.knative.dev/channel":"kafka-channel", "messaging.knative.dev/role":"controller"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

@devguyio would it make sense to move the refactoring to a separate pull request?

That would make the fix a bit more portable to older versions. So the refactoring goes in after?

@matzew I needed the refactoring to reason about that block which I need to touch and change with or without the refactoring. So I'm not very sure if without that refactoring it's gonna be more portable to older versions because that block needs to change anyway, and if it exists differently in older versions then even without the refactoring I'll have to manually fix the conflict in those versions.

/cherry-pick release-0.23

/cherry-pick release-0.24

/cherry-pick release-0.25


[miaopai] error while downloading from miaopai

annie -d http://www.miaopai.com/show/jgQhqCZaXT7ZBfkw2FXPXb1w2mvB3LFSh1CIIQ__.htm
annie: version 0.7.6, A fast, simple and clean video downloader.
 T^T
I have installed the latest version of annie on a Linux machine at home and a Mac OS X machine at work, and tried on both of them, got the same issue recently and repeatedly, for every single miaopai video. It looks more like a miaopai problem to me.
I am living in Auckland, New Zealand.
Awesome work by the way. Thank you for your time.

yeah sure, but I think it is due to Miaopai is using an invalid certificate. Would you mind implementing an optional argument to bypass security check for https requests? Something like requests.get('https://foobar.com', verify=False) in python.
That could be a temporary solution used when the same thing happens to other websites.

yeah, for now, this is the right way


Compliance /auth should be more verbose about errors

Ex. does not return any relevant information when invalid JSON is passed in AuthRequest.Data.

No information when sender is invalid.

Send a little more information when sending internal server errors.


Add the Yammer logo to the 'who is using this' section of the website.

Summary
This change adds Yammer to the list of companies that are using Jest on the website.
Test plan

Codecov Report

Merging #4971 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4971   +/-   ##
=======================================
  Coverage   60.21%   60.21%
=======================================
  Files         198      198
  Lines        6620     6620
  Branches        3        4    +1
=======================================
  Hits         3986     3986
  Misses       2634     2634

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 3d2eb37...fd31fab. Read the comment docs.

Thanks for using Jest!

Hi @cpojer.  Sorry for the noise, but can we revert this for the time being? We need to do some internal discussions and potentially submit this in a different form later.

Can you send a pull request for the revert?

From: Ben Lakey<EMAIL_ADDRESS>Sent: Thursday, November 30, 2017 4:28:55 AM
To: facebook/jest
Cc: Christoph Nakazawa; Mention
Subject: Re: [facebook/jest] Add the Yammer logo to the 'who is using this' section of the website. (#4971)
Hi @cpojerhttps://github.com/cpojer. Sorry for the noise, but can we revert this for the time being? We need to do some internal discussions and potentially submit this in a different form later.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/jest/pull/4971#issuecomment-348079489, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAA0KFjCWBe8-XHqntbw7MeoyAoPzJiNks5s7i8HgaJpZM4QsJlT.

Sure here it is: https://github.com/facebook/jest/pull/4987


missing csrf

Hello,
First off thank you for the example.
I cloned your repo and installed all the dependencies. The login page itself is loading however when I click on sign in with GitHub or with credentials nothing happens. The terminal logs out this error:
missing csrf: csrf token was missing during an action sign in.
I appreciate any help.

@M-Pedrami thanks for checking it out! I noticed this too and am working on it myself as we speak :pray:
I'll update you here once I find a solution

Let me know if your solution also works for the bun runtime.

Hi ndom91,
I saw the same behavior that you describe with your project and with my own project.
Just a minor thing that I saw is that initially when pressing the Sign In button, the route that is executed is "/api/auth/signin" instead of "/auth/signin", nothing that adds to the discussion xD.
I wonder if somehow this unexpected route and render management just makes a desynchronization of what CSFR token the server expects and what the OAuth provider is giving back.
I will try rolling back to the versions suggested to avoid this issue, thanks for the info!.

It works!, rolling back to 14.1.3 makes it work.

This is still not working for me in NextJS 14.2.3
Instead of using default signIn method that does the redirect to /api/auth/ original endpoint. I do my own link
// server action to get from `next/headers` the origin
import { SIGNIN_URL } from '$/auth'
import { headers } from 'next/headers'
import { redirect } from 'next/navigation'

export async function signinLink({ redirectTo }: { redirectTo?: string }) {
  const origin = headers().get('origin')
  const callbackUrl = redirectTo ? redirectTo : origin ?? '/'
  redirect(`${SIGNIN_URL}?callbackUrl=${callbackUrl}`)
}

And then I have a custom component that use that header
import { signinLink } from '$/auth'

function SigninLink({ redirectTo }: { redirectTo?: string }) {
  return (
    <form
      action={async (formData) => {
        'use server'
        const redirectTo = formData.get('redirectTo')?.toString()
        await signinLink({ redirectTo })
      }}
    >
      <input type='hidden' name='redirectTo' value={redirectTo} />
      <button type='submit'>Sign In</button>
    </form>
  )
}

Lastly I use that component. Note that use can pass a custom redirectTo
// My PAGE
export default function Home() {
return
}

@andresgutgon Hola Andres!! Did you get this working? I am still stuck on this :(

Hola : ) Maybe try newer version of next-auth. It's working for me now the same code

Yeah afaik this is a Next issue with 14.2.1+. Haven't had time to dig in further unfortunately.
There's a thread on the main next-auth repo as well here: https://github.com/nextauthjs/next-auth/issues/10585

The issue here is in env.ts it's setting the default config.basePath to "/api/auth" and so rather than attempting to load /auth/signin it's attempting to load /api/auth/signin, a refresh will cause it to load the proper path.
This is the code that creates the url, you can see it uses config.basePath, which defaults to /api/auth
const signInURL = createActionURL("signin",      // @ts-expect-error x-forwarded-proto is not nullable, next.js sets it by default     headers.get("x-forwarded-proto"), headers, process.env, config.basePath);

Guys I received the same error
[auth][error] MissingCSRF: CSRF token was missing during an action signin. Read more at https://errors.authjs.dev#missingcsrf at t6 (/var/task/.next/server/chunks/277.js:17:66137)     at iN (/var/task/.next/server/chunks/277.js:393:46096)     at async iz (/var/task/.next/server/chunks/277.js:393:50436)     at async /var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:34666     at async eS.execute (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:25813)     at async eS.handle (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:35920)     at async es (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:16:25461)     at async ei.responseCache.get.routeKind (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:1026)     at async r3.renderToResponseWithComponentsImpl (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:508)     at async r3.renderPageComponent (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:17:5028)
how can I fix this?
My repo: https://github.com/RushilJalal/rushil-ecommerce-store

Try this @RushilJalal https://stackoverflow.com/a/78577718

if you have tried everything and still struggle , this is the code that worked for me ( i'am using next auth v5 beta and next V14 )
this is my custom signIn page :
"use client"
import { getProviders, signIn, getCsrfToken } from "next-auth/react"
import { useEffect, useState } from "react"
import clsx from "clsx"

export default function Page() {
  const [providers, setProviders] = useState({})
  const [csrfToken, setCsrfToken] = useState("")

  useEffect(() => {
    // get the csrf token from the provider
    async function loadProviders() {
      const authProviders = await getProviders()
      setProviders(authProviders)

      const csrf = await getCsrfToken()
      setCsrfToken(csrf)
    }
    loadProviders()
  }, [])

  return (

      {/* Email / password login form */}
      <form
        className="flex flex-col bg-amber-50 p-16 rounded-lg gap-4 self-center"
        method="post"
        action="/api/auth/callback/credentials"
      >
        <input type="hidden" name="csrfToken" value={csrfToken} />

              Email
              <input className="border shadow-md" name="email" id="email" />

              Password
              <input
                className="border shadow-md"
                name="password"
                id="password"
                type="password"
              />

        <input
          type="submit"
          value="Login"
          className="bg-red-500 cursor-pointer px-3 py-1 rounded-lg font-semibold text-white"
        />
      </form>

      {/*  (Google, etc.) form */}
      {providers &&
        Object.values(providers).map((provider) => (

            <button
              onClick={() => signIn(provider.id, { callbackUrl: "/profil" })}
              className={clsx("px-3 py-1 shadow-md", {
                "bg-green-300": provider.name == "Google",
              })}
            >
              Connectez-vous avec {provider.name}
            </button>

        ))}

  )
}

and this is my auth.ts file :
import NextAuth from "next-auth"
import Google from "next-auth/providers/google"
import Credentials from "next-auth/providers/credentials"
import type { Provider } from "next-auth/providers"
import { PrismaClient } from "@prisma/client"

const prisma = new PrismaClient()

const providers: Provider[] = [
  // Credentials({
  //   credentials: { password: { label: "Password", type: "password" } },
  //   authorize(c) {
  //     if (c.password !== "password") return null
  //     return {
  //       id: "test",
  //       name: "Test User",
  //       email<EMAIL_ADDRESS>  //     }
  //   },
  // }),
  Google({
    clientId: process.env.AUTH_GOOGLE_ID,
    clientSecret: process.env.AUTH_GOOGLE_SECRET,
  }),

]

export const providerMap = providers
  .map((provider) => {
    if (typeof provider === "function") {
      const providerData = provider()
      return { id: providerData.id, name: providerData.name }
    } else {
      return { id: provider.id, name: provider.name }
    }
  })
  .filter((provider) => provider.id !== "credentials")

export const { handlers, auth, signIn, signOut } = NextAuth({
  // debug: true,
  providers,
  callbacks: {
    async signIn({ user, account, profile, credentials }) {
      console.log("Profil Google:", profile)

      const existingUser = await prisma.user.findUnique({
        where: { email: user.email },
      })

      if (!existingUser) {
        console.log("Créer un nouvel utilisateur.")
        await prisma.user.create({
          data: {
            name: user.name,
            email: user.email,
            image: user.image.replace("=s96-c", "=s400-c"),
          },
        })
      }

      return true
    },
  },

  pages: {
    signIn: "/signin",
    signOut: "/signout",
  },
})

if you have any question please let me know ;)

if you have tried everything and still struggle , this is the code that worked for me ( i'am using next auth v5 beta and next V14 ) this is my custom signIn page :
"use client"
import { getProviders, signIn, getCsrfToken } from "next-auth/react"
import { useEffect, useState } from "react"
import clsx from "clsx"

export default function Page() {
  const [providers, setProviders] = useState({})
  const [csrfToken, setCsrfToken] = useState("")

  useEffect(() => {
    // get the csrf token from the provider
    async function loadProviders() {
      const authProviders = await getProviders()
      setProviders(authProviders)

      const csrf = await getCsrfToken()
      setCsrfToken(csrf)
    }
    loadProviders()
  }, [])

  return (

      {/* Email / password login form */}
      <form
        className="flex flex-col bg-amber-50 p-16 rounded-lg gap-4 self-center"
        method="post"
        action="/api/auth/callback/credentials"
      >
        <input type="hidden" name="csrfToken" value={csrfToken} />

              Email
              <input className="border shadow-md" name="email" id="email" />

              Password
              <input
                className="border shadow-md"
                name="password"
                id="password"
                type="password"
              />

        <input
          type="submit"
          value="Login"
          className="bg-red-500 cursor-pointer px-3 py-1 rounded-lg font-semibold text-white"
        />
      </form>

      {/*  (Google, etc.) form */}
      {providers &&
        Object.values(providers).map((provider) => (

            <button
              onClick={() => signIn(provider.id, { callbackUrl: "/profil" })}
              className={clsx("px-3 py-1 shadow-md", {
                "bg-green-300": provider.name == "Google",
              })}
            >
              Connectez-vous avec {provider.name}
            </button>

        ))}

  )
}

and this is my auth.ts file :
import NextAuth from "next-auth"
import Google from "next-auth/providers/google"
import Credentials from "next-auth/providers/credentials"
import type { Provider } from "next-auth/providers"
import { PrismaClient } from "@prisma/client"

const prisma = new PrismaClient()

const providers: Provider[] = [
  // Credentials({
  //   credentials: { password: { label: "Password", type: "password" } },
  //   authorize(c) {
  //     if (c.password !== "password") return null
  //     return {
  //       id: "test",
  //       name: "Test User",
  //       email<EMAIL_ADDRESS>  //     }
  //   },
  // }),
  Google({
    clientId: process.env.AUTH_GOOGLE_ID,
    clientSecret: process.env.AUTH_GOOGLE_SECRET,
  }),

]

export const providerMap = providers
  .map((provider) => {
    if (typeof provider === "function") {
      const providerData = provider()
      return { id: providerData.id, name: providerData.name }
    } else {
      return { id: provider.id, name: provider.name }
    }
  })
  .filter((provider) => provider.id !== "credentials")

export const { handlers, auth, signIn, signOut } = NextAuth({
  // debug: true,
  providers,
  callbacks: {
    async signIn({ user, account, profile, credentials }) {
      console.log("Profil Google:", profile)

      const existingUser = await prisma.user.findUnique({
        where: { email: user.email },
      })

      if (!existingUser) {
        console.log("Créer un nouvel utilisateur.")
        await prisma.user.create({
          data: {
            name: user.name,
            email: user.email,
            image: user.image.replace("=s96-c", "=s400-c"),
          },
        })
      }

      return true
    },
  },

  pages: {
    signIn: "/signin",
    signOut: "/signout",
  },
})

if you have any question please let me know ;)

Seriously thank you, can confirm this works. I ultimately was just missing the CSRF in my form, and adding it as a hidden input works brilliantly. I know it's nice to have the library handle this, but it works and is minimal.

Originally I thought this worked, but I am deploying to Google (Firebase App Hosting), which fails even for the default (non-custom) sign in page

It of course works locally but fails in prod. I'm going to add to an existing next-auth issue, but reporting here as search brings people here.

Originally I thought this worked, but I am deploying to Google (Firebase App Hosting), which fails even for the default (non-custom) sign in page
It of course works locally but fails in prod. I'm going to add to an existing next-auth issue, but reporting here as search brings people here.

did you configured .env file ? in the hosting provider ?  also verify that sessions are working   and that this error is not related where you deployed your app .


Changed EDU token symbol to LEDU

Hi!
We (LiveEdu.tv team) have changed token symbol from EDU to LEDU. Please accept our change to the default tokens list.
Official website: http://tokensale.liveedu.tv
Support email<EMAIL_ADDRESS>Telegram: https://t.me/liveeduico

@ArtemiusUA Is there any documentation about the token symbol change?

@gamalielhere
We haven't any documentation on token symbol change, but we have LEDU mentions everywhere on our ICO site and other our resources, and also our token logo looks like "LEDU".

@ArtemiusUA Sounds good. Your FAQ mentions EDU instead of LEDU. I'll have it merged on the list I mentioned above and it should come in the next release.

@gamalielhere

Your FAQ mentions EDU instead of LEDU

Thanks! We are still in process of updating our content.


Sentry integration

This PR integrates sentry into the subnet's code.
Sentry is a toolkit that captures exceptions and sends all relevant information to a central server, where this information can be viewed in a dashboard. Sentry can integrate with github, so problems can be triaged, and allocated to teammembers.

All except statements have been hooked, as to create a full overview what is going wrong in the codebase. This means you will get unhandled (really bad) and handled exceptions (maybe bad). The unhandled ones should be resolved first, as this is a script breaking. The handled ones allow you to see if any weird stuff is happening. If the issue is not weird at all, those events can be muted in the dashboard.
In order to get this running, you will need to create an account and create a project. You will be given a trial first, then you'll need to select a paid plan or you'll get busted to the "Developer plan". This project will give you a dsn. Both validator and miner can be started with the --sentry-dsn <dsn> parameter. When this flag is enabled, sentry is enabled and will start sending information to the server.
You can  choose to withhold the dns and only run it in a test-net. However, if you make the dsn public, all participants in the network that specify the parameter will report error information. This should allow you to quickly react to fatal problems and put out patches.
I have hooked all my validators in a similar fashion, but I get so many exceptions that I can't really all SN owners of the problems, so it makes more sense to have the SN owners handled this themselves.
Note, this PR has been tested for validator only. As I don't run any miners, this should be verified for miners as well.
If you feel this PR is worthy of a reward, TAO's can go to 5FZ3Cyq4wNX6rgiTD6kSEovZ6hcvcej6N3uwV68ELb6vwQo4
Greets,
Your trusty l0lpusher69

Pull request has been stale for ~2+ months. Feel free to re-open/create a new pull request once conflicts are resolved and changes requested by @mjurbanski-reef are addressed.


opendistroforelasticsearch yum repo not updated with 1.13.3

I was just checking for updates related to log4j  and can download the tgz but the yum repo doesn't seem to have 1.13.3

This is prob a dup of https://github.com/opendistro-for-elasticsearch/opendistro-build/issues/796 but it would be nice if someone had eyes on it


When health check configs are different for targets of the same backend,one of the  health check configs is used for programming the backend.

Server version - Build from master
Service web1 has following health check configs:
"healthCheck": {
"interval": 2000,
"responseTimeout": 2000,
"healthyThreshold": 2,
"unhealthyThreshold": 3,
"requestLine": "GET /service2.html HTTP/1.0",
"port": 80,
},
Service web2 has following health check configs:
"healthCheck": {
"interval": 2000,
"responseTimeout": 2000,
"healthyThreshold": 2,
"unhealthyThreshold": 3,
"requestLine": "GET /service1.html HTTP/1.0",
"port": 80,
},
requestLine is different for both.
Created LB services for both these services. LB service uses one of the  health check config for programming the backend.

This is known issue and always been there.

Closing as we can't do anything about it. Request line for http health check gets configured on per backend on haproxy. Plus it is very unlikely that user would set 2 completely different services with different health checks behind the same backend. It would either be the same kind of service (when he does service upgrade using LB) or 2 backends, one per service.


chore: add js specific example to init strat

🚀 Deployed on https://66df37897c45f257c52fe7fd--cozy-fox-0defec.netlify.app


A DOS in sqlite-jdbc when JDBC url is user controlled

I have submitted according to the link on June 2nd(https://github.com/xerial/sqlite-jdbc/security/advisories/GHSA-rch7-2fqx-g298).Only the author can see it,but no one has replied.
Details of the vulnerability are below.
Summary
DOS when JDBC url is user controlled
Details
When JDBC is controllable by an attacker, the attacker can use the following PoC to cause a DoS attack.
jdbc:sqlite::resource:http://x.x.x.x:8000/1.sth
There is no limit to the size of the target file after testing,If the target file(1.sth) is too large, the server saves multiple tmp files after multiple requests connection.In the latest version, each tmp file name is random, and multiple tmp files can be generated with the same request url.

Impact
Dos occurs when the disk is full

Please do not open another issue after I closed the first one.