text:
Dynamic Island Installation Fails on iOS 18.1.1 – Device Link Error 205

After updating my iPhone XR from iOS 18.0 to iOS 18.1.1, the Dynamic Island feature stopped working. I attempted to reinstall the tweak using both MisakaX version 2.1.1 and 2.2. However, the installation fails with the following error log.
iOS Version: 18.1.1
iOS Name: iPhone XR
[Restore] C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data/tmp.plist -> /var/containers/Shared/SystemGroup/systemgroup.com.apple.mobilegestaltcache/Library/Caches/com.apple.MobileGestalt.plist
Traceback (most recent call last):
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\sparserestore\restore.py", line 87, in
main()
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\sparserestore\restore.py", line 46, in main
handle_exception(e, lockdown)
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\sparserestore\restore.py", line 79, in handle_exception
raise exception
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\sparserestore\restore.py", line 44, in main
restore_file(contents=e_contents, backup_path=backup_path, to_path=to_path, lockdown=lockdown)
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\python-3.12.5-embed-amd64\Lib\site-packages\exploit\restore.py", line 94, in restore_file
perform_restore(backup=back, lockdown=lockdown)
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\python-3.12.5-embed-amd64\Lib\site-packages\exploit_init_.py", line 12, in perform_restore
mb.restore(backup_dir, system=True, reboot=False, copy=False, source=".")
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\python-3.12.5-embed-amd64\Lib\site-packages\pymobiledevice3\services\mobilebackup2.py", line 140, in restore
dl.dl_loop(progress_callback)
File "C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data\python-3.12.5-embed-amd64\Lib\site-packages\pymobiledevice3\services\device_link.py", line 61, in dl_loop
raise PyMobileDevice3Exception(f'Device link error: {message[1]}')
pymobiledevice3.exceptions.PyMobileDevice3Exception: Device link error: {'ErrorCode': 205, 'ErrorDescription': 'Domain name cannot contain a slash (MBErrorDomain/205)', 'MessageName': 'Response'}
File copied successfully to C:\Users\Mukhtar Abdullahi\Downloads\misakaX-2.1.1-windows-edition\data/tmp.plist.
...
pymobiledevice3.exceptions.PyMobileDevice3Exception: Device link error: {'ErrorCode': 205, 'ErrorDescription': 'Domain name cannot contain a slash (MBErrorDomain/205)', 'MessageName': 'Response'}

您好，我知悉后 第一时间，给您回复。
                                    Wenkay


text:
Failure to encode/decode Injective types

lens is currently choking on Injective types due to the codec types not being wired up correctly in the repo. I tried to follow the same pattern as what we did for Evmos but to no avail. It seems like there is some contention in the init functions inside of Injectives SDK that cause issues when we try to work with their custom account/encoding types.
To debug the issue I've been configuring the relayer on the Juno/Injective testnets and attempting to get keys added and a light client created on both chains via the cmd: rly tx clients juno-injective-testnet -d
I was debugging the issue in this branch: https://github.com/strangelove-ventures/lens/commits/justin/injective
and then importing this into the main branch of the relayer.
I'm seeing error logs like this after running the command though
rly tx clients juno-injective-test -d
panic: ethsecp256k1.PubKey conflicts with 2 other(s). Add it to the priority list for types.PubKey.

goroutine 1 [running]:
github.com/tendermint/go-amino.(*Codec).addCheckConflictsWithConcrete_nolock(0x140011b2850, 0x140011e1560)
	/Users/justintieri/go/pkg/mod/github.com/tendermint/go-amino@v0.16.0/codec.go:683 +0x230
github.com/tendermint/go-amino.(*Codec).RegisterConcrete.func1(0x140011b2850, 0x10474eb78?)
	/Users/justintieri/go/pkg/mod/github.com/tendermint/go-amino@v0.16.0/codec.go:242 +0x60
github.com/tendermint/go-amino.(*Codec).RegisterConcrete(0x1045175a0?, {0x1046dc7e0, 0x14000130d50}, {0x103f806cf, 0x1c}, 0x103000c7c?)
	/Users/justintieri/go/pkg/mod/github.com/tendermint/go-amino@v0.16.0/codec.go:244 +0x148
github.com/cosmos/cosmos-sdk/codec.(*LegacyAmino).RegisterConcrete(...)
	/Users/justintieri/go/pkg/mod/github.com/cosmos/cosmos-sdk@v0.46.1/codec/amino.go:183
github.com/strangelove-ventures/lens/client.init.0()
	/Users/justintieri/go/src/github.com/strangelove-ventures/lens/client/keys.go:22 +0xf0

Config details for the relayer:
injective:
        type: cosmos
        value:
            key: default
            chain-id: injective-888
            rpc-addr: [https://k8s.testnet.tm.injective.network:443](https://k8s.testnet.tm.injective.network/)
            account-prefix: inj
            keyring-backend: test
            gas-adjustment: 1.2
            gas-prices: 0.00inj
            min-gas-amount: 0
            debug: false
            timeout: 60s
            output-format: json
            sign-mode: direct
    juno:
        type: cosmos
        value:
            key: default
            chain-id: uni-5
            rpc-addr: [https://juno-testnet-rpc.polkachu.com:443](https://juno-testnet-rpc.polkachu.com/)
            account-prefix: juno
            keyring-backend: test
            gas-adjustment: 1.2
            gas-prices: 0.1ujunox
            min-gas-amount: 1
            debug: false
            timeout: 20s
            output-format: json
            sign-mode: direct

They provided a branch that removes the Seal call in their SDK but that didn't seem to do the trick https://github.com/strangelove-ventures/lens/pull/205

fixed by #228

source: gharchive/issue

authors: joeabbey jtieri

repo: strangelove-ventures/lens

license_type: permissive

license_source: github-api


text:
BUG: Protected Routes omit localizations

When protecting a route, the populated localizations will always be omitted.
Using the strapi i18n Plugin does not work with protected-routes.
After manually adding the locale field in the config file, as the GUI does not support that, the field is returned.
However, the populated localizations cannot be added this way.
With an unprotected route, populating the localizations Field will return all entities with their respective locale.
When protecting the route, the population will be omitted, with no way to add it back.
I tried adding it to the populate section in the index.json to no avail.

@PrinzJuliano Will take a quick look

@PrinzJuliano Looked into it and can't replicate the is issue.
if I do.
http://localhost:1337/api/blogs?locale=nl
and api/blogs is protected I don't have any issues.

For testing:

Add more than one locale in http://localhost:1337/admin/settings/internationalization
Now create multiple translations of e.g. the blog model
When accessing http://localhost:1337/api/blogs/1?populate[0]=localizations localizations will not be populated

I see now it is correct that is blocked I will write an update this weekend what will fix this issue

Thank you very much for your work. If you need anything to further test this issue, I am more than happy to provide.
This plugin elevates some of the pain points I have in working and writing code for strapi customization.

@PrinzJuliano strapi-plugin-protected-populate@1.3.3 should fix your issue I added localizations to the UI when localization is enabled on the content-type

Thanks, I will try the update

I have tried the update and can report that everything works as expected.
Thank you very much for your work.

license: MIT


text:
Node shows non-existing connection

Right after that it disconnect:
info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0]
      Peer '[::ffff:52.233.33.138]:56354' offline, reason: 'unknown'.

This is happening regularly and that 0 height peer with the same address as the server always has a different port on every new connection.

@noescape00 I'm 99.999% sure this is happening due to this code:

Which I think is correct. We connect, then check the nonce then disconnect if its the same.

@fassadlr looks like it's not the case here- Nonces are different so when the bug happens connectedToSelf is false. Instead we have an exception during the attempt to read the magic (ReadMagicAsync => ReadBytesAsync)- the stream contains nothing when we expect it to contain 1 byte.
At the same time server spawns Unexpected exception while waiting for a message.
So it looks server shouldn't have initiated a connection in the first place (especially taking in count that server already has an inbound connection from the same peer it is trying to connect to).
So the question is: should we allow a 2 way connectivity? (I mean when there are 2 nodes- A and B. If A connects to B should the B be allowed to connect to A so both of them have 2 connections- inbound and outbound one)
I think it we want to forbid scenarios like this (and I see no reason we we wouldn't want to) we can just check on the ProcessInitialVersionPayloadAsync if the peer's Nonce is equal to any peer's Nonce that we are already connected to. And if it does- disconnect.
I think I also should investigate more in depth what is the reason for the server to initiate a connection like this on a regular basis. Maybe it has something to do with the peer discovery.

Ok. So far I've figured out that those connections are produced by the discovery jobs.
I'm pretty sure that DiscoverPeersAsync() doesn't work as it was intended since it tries to discover the same peer every 10 seconds. Maybe it's something to do with the Parallel.ForEach inside it.

I've figured it out. We never wait for the Parallel.ForEach to finish because it doesn't work properly with the awaits. So basically we are running it every 10 seconds and never await for the execution so those discovery jobs start overlapping and we end up with asking the same peers every 10 seconds or so.

repo: stratisproject/StratisBitcoinFullNode

license: mit

license_source: bigquery


text:
Pop up asking users to confirm they understand the seed words/recovery

Suggestion from the Discord: a pop up asking the wallet creator to confirm that they have stored the seed words and understand their role in the recovery of the wallet - click to confirm and move on, click to go back to the seed words.

Suggestion from the Discord: a pop up asking the wallet creator to confirm that they have stored the seed words and understand their role in the recovery of the wallet - click to confirm and move on, click to go back to the seed words.

May be unnecessary given that it asks you to input some of the words anyway?

Yes that was our intention with confirming the seed words, however a confirmation box might be helpful as well.
I'm leaving this issue open and I will discuss on adding it. Thanks.

repo: stratisproject/StratisCore


text:
[API-733] Manual Activity missing from developers.strava.com

Added the Create Activity endpoint documentation for manual activities. Stubbed out all the identifying information (hopefully)

Is that an actual response from a manual create? Surprising but makes sense

@MateoAO Yes.

Any reason why the other input parameters were omitted? http://apidocs.strava.com/internal/v3/activities/#create

So, good point. I meant to talk to you about that. If you look at the code changes, you will see that I added all the input parameters, but I think Swagger is stripping the optional ones on some basis. I tried using 'required: false' but that did not do the trick. I checked other endpoints which seem to show the same behavior.

Paging @zackisaacs

@zackisaacs @MateoAO PTAL

@zackisaacs PTAL

@zackisaacs I am not using IntelliJ. However, I think I should. I will install it sometime today and fix the weirdness.

@zackisaacs PTAL. Sorry I was too lazy to install IntelliJ. But thats the future.

source: gharchive/pull-request

authors: MateoAO hariniriyer


text:
strawberry-fastapi integration:  context['response'].background = BackgroundTask(calback) not invoked

#### gq types ####

@strawberry.type(description="mutations")
class Mutation:
    task_create = strawberry.mutation(
        resolver=task.create, description="New Task"
    )

#### deco  4 resolver  fns ####

async def user_action_audit(response):
     ...some stuff ...

def with_audit(gql_resolver: Callable[[Any], Awaitable[Any]]):
    @wraps(gql_resolver)
    async def wrapper(*args, **kwargs):
        response = await gql_resolver(*args, **kwargs)

        # https://strawberry.rocks/docs/integrations/asgi#setting-response-headers
        kwargs["info"].context["response"].set_cookie(key="kuka", value='puka')    - this WORK

        # https://strawberry.rocks/docs/integrations/asgi#setting-background-tasks  - NOT WORK(bg task NOT invoked)
        kwargs["info"].context["response"].background = BackgroundTask(user_action_audit, response)

        # was discovered myself   - WORK(bg task invoked)
        kwargs['info'].context['background_tasks'].tasks.append(BackgroundTask(user_action_audit, response))

        return response
    return wrapper

#### resolver fn ####

@with_audit
async def create(
    info: Info,
    user_id: Annotated[
        UUID, strawberry.argument(description="user id")
    ],
) -> Task:
    data = crud.task.create_for_user(info.context["db"], user_id=user_id)
    return cast(Task, data)

the problem is that no background task is called in the described here way(see comments in code)
Ubuntu 20.04
python = "~3.8"
strawberry-graphql = {extras = ["fastapi"], version = "^0.108.0"}
fastapi = "^0.75.2"

I think this is a case of out-of-date documentation as your workaround appears to be the intended functionality.
Looking at this and this, it seems impossible to achieve the functionality as described in the documentation since info.context["response"] has no attribute background. Instead, info.context has background_tasks as a field (if a dictionary) or an attribute (if inheriting from BaseContext).
I will amend the documentation to better describe this situation and so hopefully resolve this issue :D

it seems like it has, but not work(not handle), but in other case(for ex FileResponse) it works

i check - this(2) will work, but (1) in case of context['response'].background - will not

Ahh okay, interesting. I see what you're driving at! You may be mixing up the different Strawberry integrations.
You initially linked here, which actually applies to the Strawberry-ASGI integration and not the Strawberry-FastAPI integration. If you go here then you will see the correct FastAPI functionality that allows for adding background tasks to the context object, which is the functionality you desire.
Since these are different integrations, it's important that you use the correct functionality for the integration that you choose. You chose FastAPI, so you should follow these docs.

u right!
i was only google by "Setting background tasks"  )))
Thx for your time!

Great! :D If you feel that this is resolved could you please close the issue, thanks!

repo: strawberry-graphql/strawberry


text:
Add safety checks (#681)

Description

Types of Changes

[ ] Core
[x] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

#681

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to Etty for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

Think I figure out why the coverage dropped: pytest doesn't allow to have two files with the identical name in two different directories.
Also, could you please add the Oktoberfest-accepted label? tnks :)

authors: botberry estyxx


text:
CLI is currently broken

Hadn't noticed until now, would be a good first issue for someone to fix as well as adding a test to ensure it doesn't break in the future;
> duml-packet@2.0.0 cli
> ts-node dist/cli.js

file:///home/diff/repo/rednaga/dumlpacket/node_modules/yargs/lib/platform-shims/esm.mjs:38
    throw new YError(REQUIRE_DIRECTORY_ERROR)
          ^
YError: loading a directory of commands is not supported yet for ESM
    at Object.getCallerFile (file:///home/diff/repo/rednaga/dumlpacket/node_modules/yargs/lib/platform-shims/esm.mjs:38:11)
    at YargsInstance.commandDir (file:///home/diff/repo/rednaga/dumlpacket/node_modules/yargs/build/lib/yargs-factory.js:296:145)
    at file:///home/diff/repo/rednaga/dumlpacket/src/cli.ts:6:4
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

Closed via #fc46f6d

repo: strazzere/duml-packet

license: ISC


text:
Fix act warning in useAsync tests

Description

Type of change

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

Checklist

[x] Read the Contributing Guide
[x] Perform a code self-review
[x] Comment the code, particularly in hard-to-understand areas
[x] Add documentation
[x] Add hook's story at Storybook
[x] Cover changes with tests
[x] Ensure the test suite passes (yarn test)
[x] Provide 100% tests coverage
[x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
[x] Make sure types are fine (yarn lint:types).

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: streamich/react-use

license: Unlicense


text:
substreams leaks internal details to end-user

For example, if substreams fails to connet to a tier2 node, it will leak the IP address of the problem node back to the end user.
All the error messages should be sanitized to exclude any internal details.  These errors should be written to log file only.

example:
call sf.substreams.rpc.v2.Stream/Blocks: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp [2a04:fa87:fffd::c000:42a8]:9999: i/o timeout"

This won't make it in our priorities anytime soon. Is this still an issue? Can you guy do a PR?

authors: jubeless matthewdarwin

repo: streamingfast/substreams


text:
🛑 WSDL SAM Highlift is down

In 7948e79, WSDL SAM Highlift (https://wsdl-hl.streamlined-scs.cl/api/Scsdocumentos/getLogo) was down:

HTTP code: 0
Response time: 0 ms

Resolved: WSDL SAM Highlift is back up in a6ad02d.

repo: streamlined-scs/upptime


text:
🛑 WSDL SAM Highlift is down

In e2331e1, WSDL SAM Highlift (https://wsdl-hl.streamlined-scs.cl/api/Scsdocumentos/getLogo) was down:

HTTP code: 502
Response time: 3504 ms

Resolved: WSDL SAM Highlift is back up in b62c7ac.


text:
getting tweepy error

i have cloned your repo and added  to streamlit
and I also created developer API keys and secret and kept in streamlit secrets
but I am getting error in my deployment
https://mlvprasadofficial-mlv-app-twitter-analyzer-streamlit-app-cmemuj.streamlit.app/
error :
"
tweepy.errors.Forbidden: This app has encountered an error. The original error message is redacted to prevent data leaks. Full error details have been recorded in the logs (if you're on Streamlit Cloud, click on 'Manage app' in the lower right of your app).
Traceback:
File "/home/appuser/venv/lib/python3.9/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 565, in _run_script
exec(code, module.dict)
File "/app/mlv-app-twitter-analyzer/streamlit_app.py", line 443, in
tweets = search_twitter(**search_params)
File "/home/appuser/venv/lib/python3.9/site-packages/streamlit/runtime/legacy_caching/caching.py", line 629, in wrapped_func
return get_or_create_cached_value()
File "/home/appuser/venv/lib/python3.9/site-packages/streamlit/runtime/legacy_caching/caching.py", line 609, in get_or_create_cached_value
return_value = non_optional_func(*args, **kwargs)
File "/app/mlv-app-twitter-analyzer/streamlit_app.py", line 331, in search_twitter
tweets = UncacheableList(
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/cursor.py", line 86, in next
return self.next()
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/cursor.py", line 286, in next
self.current_page = next(self.page_iterator)
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/cursor.py", line 86, in next
return self.next()
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/cursor.py", line 167, in next
data = self.method(max_id=self.max_id, parser=RawParser(), *self.args, **self.kwargs)
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/api.py", line 33, in wrapper
return method(*args, **kwargs)
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/api.py", line 46, in wrapper
return method(*args, **kwargs)
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/api.py", line 1309, in search_tweets
return self.request(
File "/home/appuser/venv/lib/python3.9/site-packages/tweepy/api.py", line 265, in request
raise Forbidden(resp)
"

453 - You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated access via the Developer Portal. You can learn more here: https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api#v2-access-leve

repo: streamlit/example-app-twitter-analyzer


text:
pipelineStateHistory.json FD leak fix

pipelineStateHistory.json FD leak fix
delete pipeline on NFS share with silly rename enabled fix

Hi, @jarcec
thanks for the review
JIRA issue - SDC-9287

I believe that this issue was already addressed via a different commit, so I will resolve this one for now.

authors: jarcec pandemorra

repo: streamsets/datacollector


text:
Q: Can I completely replace the sylesheet? Trying to use bootstrap

I am trying to change the look and feel of my app to use bootstrap, but adding bootstrap CSS to the /static directory only allows me partial changing the style of the components.
THis is likely due to what you describe here: https://www.streamsync.cloud/stylesheets.html#tips-for-effective-stylesheets in that it is not using the important flag, but does that mean we are always going to have to make our own stylesheet and cannot use existing ones, like bootstrap for streamsync apps?

Yes, the expectation is for CSS classes to be created ad-hoc and used sparingly to alter small details. For example, apply rounded corners to Image.
I think your experience isn't going to be great if you apply Bootstrap to any prebuilt components. That applies to Streamsync and to any other framework that uses prebuilt components.
The only way for Bootstrap to reliably work is to create raw HTML elements that align with what Bootstrap expects. The main reason is that most of the time you'll be dealing not with raw HTML elements but with complex trees of HTML elements.
The issue you mentioned does complicate things, since style fields configurable by Builder use the style attribute of HTML elements, which has higher specificity, so things like background or color do get lost unless flagged with !important.

Hi, I'll be looking at ways to get around this limitation using Vue's SFC CSS binding
@FabienArcellier My idea is to replace the computed rootStyle and such to the v-bind in CSS, so as to have the styles have lower specificity thus not needing !important for overriding in custom stylesheets.

repo: streamsync-cloud/streamsync


text:
Simplify TestInsertState

PTAL @sttts

lgtm

authors: sttts tsenart

repo: sttts/mesos-dns


text:
Features

nezinau ar cia viskas teisingai, nes tikrai yra klaidu, bet neduoda pirma sutvarkyt, o po to duoti review. Tai labai nepykit, uz betvarke

Reiktų atsidaryti home.css "Accept incoming changes", kad išsispręstų bent dalis konfliktų.
Col-12 reiktų keisti į col-6, nes dabar abi sekcijos dalis meta vieną po kita, o ne vieną šalia kitos desktop versijoje. Po šio pataisymo bus galima žiūrėti toliau.

authors: agnekauk sauliusss

repo: student-to-dev/Omex-landing-page


text:
Process for improving working with mutable data in staging

Right now the staging environment doesn't have realistic values for mutable data that is owned by the production Student Insights instance.
This might be useful for testing, so it would be a nice-to-have feature to copy this from production each day as part of the staging workflow.  Concretely, this would be a rake task for production to dump the SQL for these tables, another rake task for staging to insert it, and a runner script to coordinate.

An initial sketch:
# Mutable data that are authoritatively owned by Student Insights
mutable_values = {
  event_notes: EventNote.all.as_json,
  services: Service.all.as_json,
  # discontinued_services: DiscontinuedService.all.as_json,
  interventions: Intervention.all.as_json,
  progress_notes: ProgressNote.all.as_json,
  student_notes: StudentNote.all.as_json,
  educators_usage: Educator.all.map do |educator|
    educator.slice(:sign_in_count, :current_sign_in_at, :last_sign_in_at, :state_id, :full_name)
  end
};nil

# Mappings between authoritative Aspen identifiers and instance-local Student Insights primary keys
identity_mappings = {
  student_school_years: StudentSchoolYear.all.as_json,
  students: Student.all.map do |student|
    student.slice(:id, :local_id, :state_id, :first_name, :last_name, :homeroom_id)
  end,
  homerooms: Homeroom.all.map do |homeroom|
    homeroom.slice(:id, :name, :slug, :grade, :educator_id)
  end,
  schools: School.all.as_json,
  educators: Educator.all.map do |educator|
    educator.slice(:id, :email, :local_id, :state_id, :full_name, :school_id)
  end
};nil

puts {
  mutable_values: mutable_values,
  identity_mappings: identity_mappings
}.to_json

Clarifying question: is this talking about copying e.g. Notes + Services from production to staging? Wouldn't that be sensitive student information?

Clarifying question: is this talking about copying e.g. Notes + Services from production to staging?

Yes, exactly.

Wouldn't that be sensitive student information?

Correct. But staging is private — just like production. It uses Somerville's LDAP system for authorization, just like production. The only public-facing website is the demo site. @erose

We don't have a staging site any more so this issue is closeable.

authors: alexsoble erose kevinrobinson

repo: studentinsights/studentinsights


text:
Improve tooltip positioner on Absences v2

Follow on to https://github.com/studentinsights/studentinsights/pull/2105
before

after

selfie


text:
Component reloads on submitting an invalid Sign-In instead of showing an error message

When I submit an invalid sign in, the component reloads instead of displaying an error message.
It is related somehow with the trigger a function called onGlobalMessage from Meteor.
Here is another gif with the debugger enabled.

I just tested it with a fresh meteor app it is working fine.
Fresh app:
https://github.com/PolGuixe/accounts-tests
As it is not related with the package I am closing it.

Fresh mantra app:
https://github.com/PolGuixe/mantra-accounts-test
And it works... defenitely us my set-up...

repo: studiointeract/accounts-ui


text:
🛑 Moodstudios is down

In 3910dc8, Moodstudios (https://moodstudios.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Moodstudios is back up in d4ebbfb after 9 minutes.

repo: studiovlijmscherp/uptime


text:
【翻译完成】20200528 Storing Empty Interfaces in BigCache

close #1744

@polaris1119 已修改

repo: studygolang/GCTT


text:
Removed Fixnum deprecated warning + Added TravisCI

As of Ruby 2.4.0, Fixnum has been deprecated and replaced with Integer. This was causing the following warning to be logged:
glutton_ratelimit-0.2.0/lib/glutton_ratelimit.rb:26: warning: constant ::Fixnum is deprecated

This PR removes this warning in a backwards compatible manner.
I've also added TravisCI configuration.

Hi James. Very sorry I didn't see this PR way back in March 2018.
Thank you kindly for this contribution. I have merged it and will release a new version of the gem later this week.

@stungeye No problem 👍

authors: JamesFrost stungeye

license: unlicense


text:
🛑 Main Site is down

In 2dec488, Main Site (https://vistacloud.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Main Site is back up in 379c67f.

repo: stxrlite/vistaclouduptime


text:
How to extend styles like styled-componets？

Styils is very convenient to use, but it seems that there is no function to extend styles in the documentation. How can I extend styles like styled-components？Looking forward to a reply.
https://styled-components.com/docs/basics#extending-styles

in vue3 , i have tried to pass other style components to styled, and the page appears to be working properly. The console prompts for some warnings, but adding CSS will fail after switching themes.
(requires manual addition !important)

export const Menu = styled("div", (theme) => ({
  display: "flex",
  gap: "20px",
  position: "sticky",
  top: "0",
  color: theme?.color,
  backgroundColor: theme?.backgroundColor,
  transition: "linear .3s",
}));

export const NMenu = styled(Menu, (theme) => ({
  top: "100px",
}));

Hi, I will investigate.

@xh4528 Already fixed in v1.1.6, if there are still problems, please feel free to reopen or create a new issue.🤞

@zoy-l  After updating v1.1.6, this issue has been resolved. Thank you for your help 👍

repo: styils/styils


text:
Question: How do I use styled-components for layout / position styles?

I have a large "Homepage" component that is made up of a lot of styled-components. So far so good.
However, I now notice that I need a few plain divs that just need styles for their position. My question is: Do I need to make components for those divs? The only property I need is something like position: relative;.
<div> <------ I need this to have position: relative, How?
  <Countdown> <------  I need this to have top: -150px, which I did using styled-components.
    <Text>COUNTDOWN</Text>
  </Countdown>
</div>

So I thought the idea of styled-components was to avoid classNames altogether? What do I do in a situation like this? It feels like it would be component overkill if I had to make a component out of absolutely everything.
Also, I don't know if top: -150px belongs in Countdown... It's weird to have positioning styles as part of the default styling of a component, since that makes it a lot less reusable.

My question is: Do I need to make components for those divs

In the strict idea of styled-components, yes! But luckily this won't be too hard:
const Wrapper = styled.div`
  position: relative;
`;

Remember that these can be "one-off" styledcomponents that are local to this one place. In that case you're only defining some styling and are colocating it with a component or some layouting.

It feels like it would be component overkill if I had to make a component out of absolutely everything.

That is exactly what we are recommending though. One StyledComponent per element, where an element would also be appropriate.

Also, I don't know if top: -150px belongs in Countdown...

Check this out :) https://www.styled-components.com/docs/advanced#referring-to-other-components

authors: EdmundMai kitten

repo: styled-components/styled-components


text:
CRA production build, no style

Hi,
I have an app bootstrapped by CRA.
But I have a bug currently: when I build for production (yarn build), the result is not styled, while there is no problem in a dev server (yarn start).
version:
styled-components: 5.0.1
babel-plugin-macro: 2.8.0
CRA (react-scripts): 3.4.1
react: 16.12.0
package.json
{
  "name": "xxx",
  "version": "0.1.1",
  "private": true,
  "scripts": {
    "analyze": "source-map-explorer build/static/js/main.*",
    "extract-intl": "babel-node ./internals/scripts/extract-intl.js",
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test --env=jest-environment-jsdom-sixteen",
    "eject": "react-scripts eject",
    "lint": "npx eslint ."
  },
  "devDependencies": {
    "@apollo/react-testing": "^3.1.3",
    "@babel/cli": "^7.6.0",
    "@babel/core": "^7.6.0",
    "@babel/node": "^7.0.0",
    "@testing-library/jest-dom": "^5.1.1",
    "@testing-library/react": "^10.0.1",
    "babel-plugin-macros": "^2.8.0",
    "babel-plugin-react-intl": "^7.5.0",
    "enzyme": "^3.1.0",
    "enzyme-adapter-react-16": "^1.0.2",
    "eslint-plugin-react": "^7.18.0",
    "intl": "^1.2.5",
    "jest-environment-jsdom-sixteen": "^1.0.3",
    "jest-styled-components": "^7.0.0",
    "jest-teamcity-reporter": "^0.9.0",
    "json-format": "^1.0.1",
    "mocha": "^7.0.0",
    "mock-socket": "^9.0.3",
    "react-router-enzyme-context": "^1.2.0",
    "react-test-renderer": "^16.3.2",
    "redux-mock-store": "^1.3.0",
    "shelljs": "^0.8.3"
  },
  "dependencies": {
    "@apollo/react-hooks": "^3.1.2",
    "@blueprintjs/datetime": "^3.15.2",
    "@formatjs/intl-utils": "^2.0.4",
    "@fortawesome/fontawesome-svg-core": "^1.2.4",
    "@fortawesome/free-brands-svg-icons": "^5.5.0",
    "@fortawesome/free-regular-svg-icons": "^5.3.1",
    "@fortawesome/free-solid-svg-icons": "^5.3.1",
    "@fortawesome/react-fontawesome": "^0.1.3",
    "antd": "^4.0.0",
    "apollo-client": "^2.6.8",
    "aw-common-ui": "0.1.0-factoring-component-test",
    "classnames": "^2.2.6",
    "graphql-tag": "^2.10.1",
    "immutability-helper": "^3.0.1",
    "lodash": "^4.17.15",
    "moment": "^2.24.0",
    "moment-duration-format": "^2.2.2",
    "node-sass": "^4.13.0",
    "owp-core-ui": "0.15.7-add-registry",
    "prop-types": "^15.7.2",
    "react": "^16.12.0",
    "react-apollo": "^3.1.3",
    "react-big-calendar": "0.22.1",
    "react-debounce-input": "^3.2.0",
    "react-dom": "^16.12.0",
    "react-dotdotdot": "^1.2.3",
    "react-dropzone-component": "^3.2.0",
    "react-highcharts": "^16.0.2",
    "react-html5-camera-photo": "^1.2.9",
    "react-idle-timer": "^4.0.4",
    "react-intl": "^4.4.0",
    "react-intl-formatted-duration": "^3.1.0",
    "react-lines-ellipsis": "^0.14.1",
    "react-markdown": "^4.3.1",
    "react-placeholder": "^4.0.1",
    "react-redux": "^7.1.3",
    "react-router": "^5.1.2",
    "react-router-dom": "^5.1.2",
    "react-rte": "^0.16.1",
    "react-scripts": "3.4.1",
    "react-select": "^3.0.8",
    "react-tag-cloud": "1.3.2",
    "reactstrap": "^8.2.0",
    "recompose": "^0.30.0",
    "seamless-immutable": "7.1.4",
    "styled-components": "^5.0.1",
    "styled-system": "^5.1.5",
    "validator": "^13.0.0",
    "velocity-react": "^1.4.1"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

In the the DOM, if I look the class names, I can see that the good classes produced by the styled components are there. I use your babel macro. I also tested without the babel plugin and no styled-components/macro imports but this does not help.
I'm not sure if the problem comes from that, but I noticed in the output of the yarn build command, in static/css/ there is 9 css chunks. Whereas in index.html, head tag, there is only 2 chunks injected through the link tags.
I don't know what is causing this bug. Even If it's relevant to CRA or styled component.
Have you an idea ?
edit: I tried to include myself the chunks eg <link href="/static/css/main.c2797778.chunk.css" rel="stylesheet"> in the HTML head. This did not resolve the problem.

I was having this exact same issue, and solved it by removing my CSS @import statements.
More here: https://github.com/styled-components/styled-components/issues/2911#issuecomment-592012166
This seems like an issue caused by v5.0.1 and above.

I'm having the same issue with upgrading from v4 to v5, everything works fine locally but styles do not work in some places only in production. Was fine in v4

Please refer with usage questions to Stack Overflow, as you're more likely to get quicker and helpful answers there ❤ Repository issues on GitHub are great for that, issues, things that need to be resolved in the library itself, or can't be resolved by anyone but the maintainers. While I (and many others on other repos) are happy to eventually answer usage questions, styled-components is a busy repo and mostly stable and slow moving towards new releases, so you're not likely to get fast responses here

authors: doums kitten malimccalla nkhil


text:
[styled-components] add ThemeProvider to Example

Problem:

quick working example that I can quickly modify the check if theming works correctly

Solution:

add ThemeProvider to devServer Example

@sulmanen you might want to do this against canary instead, or the work will be lost when we do the v5 release

authors: probablyup sulmanen


text:
onClick event not working on styled components

Hi there
I have just experienced another weird bug.
I originally had something like this:
return (
  <button type='button' class={(isOpen ? ' is-open' : '')} onClick={toggleMenu} aria-label='Open Menu'>

  </button>
)

This was when I used this with sass. I switched to vue styled components and rewrote that code to:
return (
  <Button type='button' onClick={toggleMenu} aria-label='Open Menu'>
    <Burger class={(isOpen ? ' is-open' : '')}></Burger>
  </Button>
)

The problem is, that now the click event is not triggered anymore.
It would only trigger if I wrap the thing with a div and assign the click onto the div:
return (

    <Button type='button' aria-label='Open Menu'>
      <Burger class={(isOpen ? ' is-open' : '')}></Burger>
    </Button>

)

I guess it must be because of the styled components, but I don't know why.
If anyone could help me out here, I would be very glad.
Cheers
-------------- Edit ------------
And I just tested this case as well to minimize error sources:
return (
  <Testdiv onClick={click}>
    <Button type='button' aria-label='Open Menu'>
      <Burger class={(isOpen ? ' is-open' : '')}></Burger>
    </Button>
  </Testdiv>
)

While I kept everything as it was in the working example with the wrapperdiv, but just used a styled div like this:
export const Testdiv = styled.div`

`

Then the click suddenly stops working

Hi @Jones-S
first of all, you are using jsx with vue right?
Never tried with jsx for now.
Maybe the context of the execution it's wrong, can be?

Hi @Jones-S,
referring to https://forum.vuejs.org/t/events-not-triggered-on-component/13173/3 this post, you have to use @click.native to use click event on a custom component. :)

Thanks man. I could get it to work. Now I will try to understand what happens :)
    return (
      <Button nativeOnClick={toggleMenu} type='button' aria-label='Open Menu'>
        <Burger class={(isOpen ? ' is-open' : '')}></Burger>
      </Button>
    )

Thanks for this, had a similar problem, this post just helped! :)

authors: Ayngie Jones-S liqueflies

repo: styled-components/vue-styled-components


text:
Faker::Number.number(6) gives Segmentation fault at 0x00

I have a Rails app where I'm generating a PIN for my user
current_user.update_column :pin_code, Faker::Number.number(6)

but I'm getting this:
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/faker-1.9.1/lib/faker.rb:218: [BUG] Segmentation fault at 0x00000000000000
ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin16]

-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:
     * ~/Library/Logs/CrashReporter
     * /Library/Logs/CrashReporter
     * ~/Library/Logs/DiagnosticReports
     * /Library/Logs/DiagnosticReports
   for more details.
Don't forget to include the above Crash Report log file in bug reports.

-- Control frame information -----------------------------------------------
c:0082 p:---- s:0564 e:000563 CFUNC  :rand
c:0081 p:0079 s:0559 e:000558 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/faker-1.9.1/lib/faker.rb:218
c:0080 p:0010 s:0554 e:000553 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/faker-1.9.1/lib/faker/number.rb:33
c:0079 p:0028 s:0550 e:000549 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/faker-1.9.1/lib/faker/number.rb:7
c:0078 p:0024 s:0544 e:000541 METHOD /Users/bruckerts/projects/project/apps/my_file.rb:5
c:0077 p:0014 s:0538 e:000537 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal/basic_implicit_render.rb:6
c:0076 p:0014 s:0532 e:000531 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/abstract_controller/base.rb:194
c:0075 p:0035 s:0526 e:000525 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal/rendering.rb:30
c:0074 p:0012 s:0521 e:000520 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/abstract_controller/callbacks.rb:42
c:0073 p:0134 s:0518 E:001a18 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/callbacks.rb:132
c:0072 p:0011 s:0508 E:001998 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/abstract_controller/callbacks.rb:41
c:0071 p:0012 s:0503 e:000502 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal/rescue.rb:22
c:0070 p:0014 s:0497 e:000496 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal/instrumentation.rb:34
c:0069 p:0014 s:0492 e:000491 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/notifications.rb:168
c:0068 p:0028 s:0489 e:000488 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/notifications/instrumenter.rb:23
c:0067 p:0033 s:0481 e:000480 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/notifications.rb:168
c:0066 p:0112 s:0475 e:000474 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal/instrumentation.rb:32
c:0065 p:0116 s:0469 e:000468 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal/params_wrapper.rb:256
c:0064 p:0029 s:0461 e:000460 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activerecord-5.2.1/lib/active_record/railties/controller_runtime.rb:24
c:0063 p:0077 s:0455 e:000454 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/abstract_controller/base.rb:134
c:0062 p:0028 s:0448 e:000447 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal.rb:191
c:0061 p:0050 s:0441 e:000440 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_controller/metal.rb:252
c:0060 p:0015 s:0434 e:000433 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/routing/route_set.rb:52
c:0059 p:0051 s:0426 e:000425 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/routing/route_set.rb:34
c:0058 p:0011 s:0418 e:000417 LAMBDA /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/routing/mapper.rb:18 [FINISH]
c:0057 p:0042 s:0413 e:000412 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/routing/mapper.rb:48
c:0056 p:0155 s:0408 e:000407 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/journey/router.rb:52 [FINISH]
c:0055 p:---- s:0396 e:000395 CFUNC  :each
c:0054 p:0014 s:0392 e:000391 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/journey/router.rb:35
c:0053 p:0049 s:0387 e:000386 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/routing/route_set.rb:840
c:0052 p:0208 s:0381 e:000380 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/omniauth-1.8.1/lib/omniauth/strategy.rb:190
c:0051 p:0013 s:0375 e:000374 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/omniauth-1.8.1/lib/omniauth/strategy.rb:168
c:0050 p:0208 s:0370 e:000369 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/omniauth-1.8.1/lib/omniauth/strategy.rb:190
c:0049 p:0013 s:0364 e:000363 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/omniauth-1.8.1/lib/omniauth/strategy.rb:168
c:0048 p:0013 s:0359 e:000358 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/omniauth-1.8.1/lib/omniauth/builder.rb:63
c:0047 p:0140 s:0354 e:000353 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-attack-5.4.0/lib/rack/attack.rb:181
c:0046 p:0053 s:0348 e:000347 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/pdfkit-0.8.2/lib/pdfkit/middleware.rb:16
c:0045 p:0038 s:0339 e:000338 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/session/abstract/id.rb:232
c:0044 p:0010 s:0328 e:000327 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/session/abstract/id.rb:226
c:0043 p:0030 s:0323 e:000322 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/cookies.rb:670
c:0042 p:0012 s:0313 e:000312 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/warden-1.2.7/lib/warden/manager.rb:36 [FINISH]
c:0041 p:---- s:0310 e:000309 CFUNC  :catch
c:0040 p:0073 s:0305 e:000304 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/warden-1.2.7/lib/warden/manager.rb:35
c:0039 p:0012 s:0299 e:000298 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/etag.rb:25
c:0038 p:0045 s:0288 e:000287 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/conditional_get.rb:38
c:0037 p:0012 s:0279 e:000278 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/head.rb:12
c:0036 p:0078 s:0271 e:000270 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activerecord-5.2.1/lib/active_record/migration.rb:559
c:0035 p:0014 s:0265 e:000264 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/callbacks.rb:28
c:0034 p:0037 s:0262 e:000261 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/callbacks.rb:98
c:0033 p:0016 s:0253 e:000252 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/callbacks.rb:26
c:0032 p:0024 s:0246 e:000245 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/executor.rb:14
c:0031 p:0064 s:0238 e:000237 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/bugsnag-6.8.0/lib/bugsnag/integrations/rack.rb:46
c:0030 p:0012 s:0231 e:000230 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/better_errors-2.4.0/lib/better_errors/middleware.rb:84
c:0029 p:0033 s:0225 e:000224 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/better_errors-2.4.0/lib/better_errors/middleware.rb:79
c:0028 p:0020 s:0220 e:000219 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/better_errors-2.4.0/lib/better_errors/middleware.rb:57
c:0027 p:0030 s:0215 e:000214 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/debug_exceptions.rb:61
c:0026 p:0030 s:0204 e:000203 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/show_exceptions.rb:33
c:0025 p:0012 s:0197 e:000196 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/chewy-5.0.0/lib/chewy/railtie.rb:19
c:0024 p:0016 s:0194 e:000193 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/chewy-5.0.0/lib/chewy/strategy.rb:70
c:0023 p:0085 s:0188 e:000187 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/chewy-5.0.0/lib/chewy.rb:201
c:0022 p:0169 s:0182 E:000358 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/chewy-5.0.0/lib/chewy/railtie.rb:19
c:0021 p:0051 s:0177 E:001430 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/railties-5.2.1/lib/rails/rack/logger.rb:38
c:0020 p:0012 s:0167 e:000166 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/railties-5.2.1/lib/rails/rack/logger.rb:26
c:0019 p:0007 s:0164 e:000163 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/tagged_logging.rb:71
c:0018 p:0019 s:0161 e:000160 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/tagged_logging.rb:28
c:0017 p:0016 s:0155 e:000154 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/tagged_logging.rb:71
c:0016 p:0049 s:0150 e:000149 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/railties-5.2.1/lib/rails/rack/logger.rb:26
c:0015 p:0061 s:0144 e:000143 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/remote_ip.rb:81
c:0014 p:0047 s:0138 e:000137 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/request_id.rb:27
c:0013 p:0026 s:0132 e:000131 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/runtime.rb:22
c:0012 p:0039 s:0122 e:000121 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/cache/strategy/local_cache_middleware.rb:29
c:0011 p:0024 s:0115 e:000114 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/executor.rb:14
c:0010 p:0103 s:0107 e:000106 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/static.rb:127
c:0009 p:0012 s:0099 e:000098 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/sendfile.rb:111
c:0008 p:0230 s:0087 E:002478 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-cors-1.0.2/lib/rack/cors.rb:97
c:0007 p:0026 s:0074 e:000073 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/railties-5.2.1/lib/rails/engine.rb:524
c:0006 p:0032 s:0068 e:000067 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/configuration.rb:225
c:0005 p:0302 s:0063 e:000062 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/server.rb:658
c:0004 p:0040 s:0038 e:000037 METHOD /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/server.rb:472
c:0003 p:0084 s:0026 e:000025 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/server.rb:332 [FINISH]
c:0002 p:0160 s:0016 e:000015 BLOCK  /Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/thread_pool.rb:133 [FINISH]
c:0001 p:---- s:0003 e:000002 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/thread_pool.rb:133:in `block in spawn_thread'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/server.rb:332:in `block in run'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/server.rb:472:in `process_client'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/server.rb:658:in `handle_request'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/puma-3.12.0/lib/puma/configuration.rb:225:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/railties-5.2.1/lib/rails/engine.rb:524:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-cors-1.0.2/lib/rack/cors.rb:97:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/sendfile.rb:111:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/static.rb:127:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/executor.rb:14:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/rack-2.0.5/lib/rack/runtime.rb:22:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/request_id.rb:27:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/actionpack-5.2.1/lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/railties-5.2.1/lib/rails/rack/logger.rb:26:in `call'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/tagged_logging.rb:71:in `tagged'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/tagged_logging.rb:28:in `tagged'
/Users/bruckerts/.rvm/gems/ruby-2.4.0/gems/activesupport-5.2.1/lib/active_support/tagged_logging.rb:71:in `block in tagged'

It looks to me as I am using this function correctly? https://github.com/stympy/faker/blob/master/doc/number.md
Thanks for your help

Thanks for posting this issue.
Unfortunately I can't reproduce this bug locally. Could you provide a sample application for us?

authors: stephanebruckert vbrazo

repo: stympy/faker


text:
Tracking bei Nextcloud 9.0.52 (stable)

Piwik läuft unter https://analytics.domain1.tdl/ und Nextcloud unter https://cloud.domain2.tdl/ aber es werden keine Daten gesammelt.
Bei Nextcloud wurde auch die .htaccess angepasst und unter  RewriteRule "^piwik/(.*)$" "https://analyics.domain1.tdl/$1" [P] eingefügt.
Woran hängt es nun?

Nachdem bei Nextcloud im Admin die Piwik URL von https://analytics.domain1.tdl/ auf //analytics.domain1.tdl/ geändert wurde. geht nun alles ;)

zu früh gefreut... habe gerade bemerkt das nur die Login-Seite getrackt wird...

Versuchs mal mit "/piwik/" als URL. Ansonsten sollte ein Blick in die JS Console helfen.

Irgendwelche Updates, oder kann man das Ticket schließen?


text:
Feat: Update/Edit profile

Describe the feature
Add bio
edit email
edit name
edit username
edit userProfile
and other use full field's
Add ScreenShots
current:

proposal:

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Vaibhavsg17 Add new "/dashboard/settings" page instead

@Vaibhavsg17 Add new "/dashboard/settings" page instead

Yes


text:
Make the Copyright Year Dynamic

Is your proposal related to a problem?
Currently, the copyright year is hardcoded as 2024 in the footer section. This creates a maintenance burden since it has to be updated manually every year
Describe the solution you'd like
I would like to make the copyright year dynamic. By using JavaScript, the year can be fetched automatically, ensuring that it always reflects the current year without manual intervention.
Describe alternatives you've considered
I considered leaving the hardcoded year and simply updating it manually each year, but this approach is prone to human error and inefficiency.
Additional context
This solution would improve the maintainability of the footer. A similar issue has been raised in another repository where I contributed a dynamic solution. This would bring consistency across projects and save time for future updates.
Here is a screenshot showing the hardcoded 2024 year in the footer section of the code:

Requirement/Document
No specific document is required for this feature; it's a straightforward implementation using JavaScript.

/assign

repo: subhadipbhowmik/bio-branch


text:
🛑 Cubari (MangaDex) is down

In 4d2b79d, Cubari (MangaDex) (https://cubari.moe/read/mangadex/d86cf65b-5f6c-437d-a0af-19a31f94ec55/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 500
Response time: 221 ms

Resolved: Cubari (MangaDex) is back up in 83814a4 after 6 minutes.

repo: subject-f/cubari-status-page


text:
🛑 Cubari (NHentai) is down

In b537dc5, Cubari (NHentai) (https://cubari.moe/read/nhentai/381867/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cubari (NHentai) is back up in 19f0b1f after 1 hour, 34 minutes.


text:
Reconcile clustersetip in broker

Reconcile clustersetip in BrokerReconciler

@tpantelis We discussed this earlier and not 100% sure we will need this. Pushing this PR for now in case we do need it for addon reconcilation.

repo: submariner-io/submariner-operator


text:
Correct "on-premise" to "on-premises"

It turns out this is a grammar mistake. Premise is related to logic and
statements only, premises is the location-related term we wanted.
Signed-off-by: Daniel Farrell dfarrell@redhat.com

on-premise sounds correct/better but I/m OK either way.

It sounds good/normal to me too, but I think @nyechiel correctly pointed out that it's actually a totally different word, not the plural/singular situation I thought.
https://collectivecontent.co.uk/2018/04/19/should-i-say-on-premise-or-on-premises-it/
https://www.cloudelicious.net/when-grammar-is-becoming-a-challenge-on-premise-vs-on-premises/

repo: submariner-io/submariner-website


text:
Optimization: Better word fast-path detection

Just doing an indexOf check could still match "requires", "required", "requirejs", etc. By using a conservative regexp we can decrease the likelihood of a false positive. (And I think a cached regexp is faster than indexOf http://jsperf.com/substring-test/3).
cc: @substack

I had a better regexp for the common "require" case with no "isRequire" - which is why the test is so crazy. Let me know if you're open to it:
/(^|\W)require(\s*|\/\*[^*]*\*\/|\/\/[^\n]*)*\(/
   ^     ^    ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^  ^
   |     |    |                            |  |
   |     |    |                            |  + open parens
   |     |    |                            v
   |     |    + (spaces | block comments | line comments) any number of times
   |   + our word
   + start or anything not [a-zA-Z_]

Another optimization I've thought about would be to use https://github.com/dominictarr/js-tokenizer instead of a full AST.

authors: substack zertosh

repo: substack/node-detective


text:
Compile Problem?

GOPATH=/root/vmango/vendor:/root/vmango go build -o vendor/bin/go-bindata github.com/jteeuwen/go-bindata/go-bindata
/bin/sh: 1: go: not found
Makefile:28: recipe for target 'vendor/bin/go-bindata' failed
make: *** [vendor/bin/go-bindata] Error 127
Debian 8

Ok is fixed with this
cd /tmp
wget https://dl.google.com/go/go1.9.4.linux-amd64.tar.gz -q
tar -xzf go1.9.4.linux-amd64.tar.gz
mv go /usr/local
export GOROOT=/usr/local/go
export GOPATH=$HOME/Projects/Proj1
export PATH=$GOPATH/bin:$GOROOT/bin:$PATH
go version
go env
cd ~/
and : apt-get install gcc
make

repo: subuk/vmango


text:
Incorrect messages of states of environments

Fixed.

Fixed prod.

repo: subutai-io/control-center


text:
Tray on OSX doesn't respect text box entry

On macOS/OSX if you type a path into one of the binary text box or copy/paste for example /usr/local/bin/VBoxManage into the field, Tray doesn't register or save the changes.
However if you navigate to the binary with the [...] button the Tray application records the change and respects it.

@BenjaminHCCarr I couldn't reproduce this on MacOS Sierra 10.12.6 with latest (6.2.0) tray. I was playing with path to p2p and it saves hand written path without problems.

@BenjaminHCCarr Can you paste it by right click->Paste? And if it works then this issue could be because of some minor updates in OS X. I have found out that some MAC users have copy/paste issues for some fields and they overcome the problem by updating.

Fixed.

repo: subutai-io/tray


text:
A simpler solution to the problem of focus?

TL;DR: There's another bug with handling focus when clicking on a toolbar button. I think there may be a simpler solution.
Tool Bar tries to behave as if the command that the toolbar button triggers was triggered from whatever had focus before the user clicked. As a result, Tool Bar actively gives focus to the DOM node that was focused before the user moved their mouse into the toolbar. Unfortunately giving a nodes can have side effects. For example, a pane will reveal itself when it receives focus.
This causes a bug, which can be reproduces by:

Have two Panels: PanelA and PanelB which are both in a visible dock
Focus PanelA
Move mouse to the toolbar (prevFocusedElm is now PanelA)
Click button which toggle's PanelB (PanelB is now focused)
Click button which toggle's PanelB (The dock containing PanelA is hidden)
Click button which toggle's PanelB

What happens now is:

prevFocusedElm (which is still PanelA) gets focused, causing the dock (and PanelB) to become visible
The command which toggles PanelB is now called with PanelB visible, so it closes PanelB instead of opening it

The net effect is that the third (and any subsequent) clicks in the toolbar do nothing, and the feature seems broken.
Proposed Solution
Rather than taking focus and then attempting to return it, what if wen never took that focus in the first place?
By calling e.preventDefault in a mousedown handler, we can avoid taking focus, and therefore we never have to return it. We may even be able to avoid tracking prevFocusedElm all together.
If this solution seems reasonable, I'm happy to open a pull request.
I think @AnWeber alluded to this issue on a comment here back in 2016: https://github.com/suda/tool-bar/pull/88

Ping @suda. This is affecting us on Nuclide.

Hey, sorry for not responding to this issue! That sounds like a good way to go so feel free to create the PR!

@suda I've opened https://github.com/suda/tool-bar/pull/239. Let me know what you think.

authors: captbaritone suda

repo: suda/tool-bar


text:
shloka number overlap with mobile top line

See attached pic.
Move the shloka number a little down
Or
Hide the mobile top line

Solved by increasing height of headings

repo: sudeeprp/GitaPower


text:
Add support for Ubuntu.

Add screenshot and installation guideline.

Add screenshot and installation guideline.

Add screenshot and installation guideline.

There is no requirement of configuring firefo browser to function as webdriver.It works fine after the installation of web driver for firefox.

authors: pateldevang sudnyeshtalekar

repo: sudnyeshtalekar/Whatsapp-Message-bomber


text:
Crash on village generate

Minecraft versions

1.19.2
forge 43.3.0

Mod versions

create -- 0.5.1.e
create: dynamic village -- 0.2.1 & 0.2

Error logs
[21:11:34] [Server thread/ERROR] [minecraft/MinecraftServer]: Exception stopping the server
java.util.concurrent.CompletionException: net.minecraft.ReportedException: Feature placement
	at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315) ~[?:?] {re:mixin}
	at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320) ~[?:?] {re:mixin}
	at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1159) ~[?:?] {}
	at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482) ~[?:?] {}
	at net.minecraft.server.level.ChunkTaskPriorityQueueSorter.m_143188_(ChunkTaskPriorityQueueSorter.java:62) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:classloading}
	at net.minecraft.util.thread.ProcessorMailbox.m_18759_(ProcessorMailbox.java:91) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:classloading}
	at net.minecraft.util.thread.ProcessorMailbox.m_18747_(ProcessorMailbox.java:146) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:classloading}
	at net.minecraft.util.thread.ProcessorMailbox.run(ProcessorMailbox.java:102) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:classloading}
	at java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(ForkJoinTask.java:1395) ~[?:?] {}
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) ~[?:?] {}
	at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) ~[?:?] {}
	at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) ~[?:?] {re:mixin,re:computing_frames}
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) ~[?:?] {re:mixin,re:computing_frames}
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) ~[?:?] {re:mixin}
Caused by: net.minecraft.ReportedException: Feature placement
	at net.minecraft.server.level.ChunkMap.lambda$scheduleChunkGeneration$25(ChunkMap.java:636) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:modernfix-common.mixins.json:bugfix.paper_chunk_patches.ChunkMapMixin,pl:mixin:APP:modernfix-forge.mixins.json:bugfix.chunk_deadlock.ChunkMapLoadMixin,pl:mixin:APP:canary.mixins.json:world.player_chunk_tick.ChunkMapMixin,pl:mixin:APP:railways.mixins.json:ChunkMapAccessor,pl:mixin:APP:ftbchunks-common.mixins.json:ChunkMapMixin,pl:mixin:APP:railways-common.mixins.json:conductor_possession.ChunkMapMixin,pl:mixin:A}
	at com.mojang.datafixers.util.Either$Left.map(Either.java:38) ~[datafixerupper-5.0.28.jar%23121!/:?] {}
	at net.minecraft.server.level.ChunkMap.lambda$scheduleChunkGeneration$27(ChunkMap.java:619) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:modernfix-common.mixins.json:bugfix.paper_chunk_patches.ChunkMapMixin,pl:mixin:APP:modernfix-forge.mixins.json:bugfix.chunk_deadlock.ChunkMapLoadMixin,pl:mixin:APP:canary.mixins.json:world.player_chunk_tick.ChunkMapMixin,pl:mixin:APP:railways.mixins.json:ChunkMapAccessor,pl:mixin:APP:ftbchunks-common.mixins.json:ChunkMapMixin,pl:mixin:APP:railways-common.mixins.json:conductor_possession.ChunkMapMixin,pl:mixin:A}
	at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150) ~[?:?] {}
	... 11 more
Caused by: java.lang.RuntimeException: com.mojang.brigadier.exceptions.CommandSyntaxException: Unknown block type 'create:andesite_bricks' at position 0: <--[HERE]
	at net.minecraft.world.level.levelgen.structure.templatesystem.JigsawReplacementProcessor.m_7382_(JigsawReplacementProcessor.java:38) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:classloading}
	at net.minecraft.world.level.levelgen.structure.templatesystem.StructureProcessor.process(StructureProcessor.java:18) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,re:classloading,pl:mixin:APP:repurposed_structures.mixins.json:structures.StructureProcessorAccessor,pl:mixin:APP:betterjungletemples.mixins.json:accessor.StructureProcessorAccessor,pl:mixin:APP:betterwitchhuts.mixins.json:accessor.StructureProcessorAccessor,pl:mixin:APP:betteroceanmonuments.mixins.json:accessor.StructureProcessorAccessor,pl:mixin:APP:betterdeserttemples.mixins.json:accessor.StructureProcessorAccessor,pl:mixin:A}
	at net.minecraft.world.level.levelgen.structure.templatesystem.StructureTemplate.processBlockInfos(StructureTemplate.java:378) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at net.minecraft.world.level.levelgen.structure.templatesystem.StructureTemplate.m_230328_(StructureTemplate.java:225) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:A}
	at net.minecraft.world.level.levelgen.structure.pools.SinglePoolElement.m_213695_(SinglePoolElement.java:127) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:yungsapi.mixins.json:accessor.SinglePoolElementAccessor,pl:mixin:APP:repurposed_structures.mixins.json:structures.SinglePoolElementAccessor,pl:mixin:APP:betterstrongholds.mixins.json:accessor.SinglePoolElementAccessor,pl:mixin:APP:waystones.mixins.json:SinglePoolElementMixin,pl:mixin:A}
	at net.minecraft.world.level.levelgen.structure.PoolElementStructurePiece.m_226509_(PoolElementStructurePiece.java:89) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:repurposed_structures.mixins.json:structures.PoolElementStructurePieceAccessor,pl:mixin:A}
	at net.minecraft.world.level.levelgen.structure.PoolElementStructurePiece.m_213694_(PoolElementStructurePiece.java:85) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:repurposed_structures.mixins.json:structures.PoolElementStructurePieceAccessor,pl:mixin:A}
	at net.minecraft.world.level.levelgen.structure.StructureStart.m_226850_(StructureStart.java:89) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,re:classloading,pl:mixin:A}
	at net.minecraft.world.level.chunk.ChunkGenerator.m_223080_(ChunkGenerator.java:429) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:modernfix-common.mixins.json:perf.cache_strongholds.ChunkGeneratorMixin,pl:mixin:APP:betterfortresses.mixins.json:DisableVanillaFortressesMixin,pl:mixin:APP:structure_gel.mixins.json:ChunkGeneratorMixin,pl:mixin:APP:bettermineshafts.mixins.json:DisableVanillaMineshaftsMixin,pl:mixin:APP:betterjungletemples.mixins.json:DisableVanillaJungleTempleMixin,pl:mixin:APP:betterwitchhuts.mixins.json:DisableVanillaWitchHutsMixin,pl:mixin:APP:betteroceanmonuments.mixins.json:DisableVanillaMonumentsMixin,pl:mixin:APP:betterstrongholds.mixins.json:DisableVanillaStrongholdsMixin,pl:mixin:APP:betterdeserttemples.mixins.json:DisableVanillaPyramidsMixin,pl:mixin:A}
	at com.google.common.collect.ImmutableList.forEach(ImmutableList.java:422) ~[guava-31.0.1-jre.jar%23116!/:?] {re:mixin}
	at net.minecraft.world.level.chunk.ChunkGenerator.m_213609_(ChunkGenerator.java:428) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:modernfix-common.mixins.json:perf.cache_strongholds.ChunkGeneratorMixin,pl:mixin:APP:betterfortresses.mixins.json:DisableVanillaFortressesMixin,pl:mixin:APP:structure_gel.mixins.json:ChunkGeneratorMixin,pl:mixin:APP:bettermineshafts.mixins.json:DisableVanillaMineshaftsMixin,pl:mixin:APP:betterjungletemples.mixins.json:DisableVanillaJungleTempleMixin,pl:mixin:APP:betterwitchhuts.mixins.json:DisableVanillaWitchHutsMixin,pl:mixin:APP:betteroceanmonuments.mixins.json:DisableVanillaMonumentsMixin,pl:mixin:APP:betterstrongholds.mixins.json:DisableVanillaStrongholdsMixin,pl:mixin:APP:betterdeserttemples.mixins.json:DisableVanillaPyramidsMixin,pl:mixin:A}
	at net.minecraft.world.level.chunk.ChunkStatus.m_223313_(ChunkStatus.java:145) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B}
	at net.minecraft.world.level.chunk.ChunkStatus.m_223279_(ChunkStatus.java:292) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B}
	at net.minecraft.server.level.ChunkMap.lambda$scheduleChunkGeneration$25(ChunkMap.java:621) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:modernfix-common.mixins.json:bugfix.paper_chunk_patches.ChunkMapMixin,pl:mixin:APP:modernfix-forge.mixins.json:bugfix.chunk_deadlock.ChunkMapLoadMixin,pl:mixin:APP:canary.mixins.json:world.player_chunk_tick.ChunkMapMixin,pl:mixin:APP:railways.mixins.json:ChunkMapAccessor,pl:mixin:APP:ftbchunks-common.mixins.json:ChunkMapMixin,pl:mixin:APP:railways-common.mixins.json:conductor_possession.ChunkMapMixin,pl:mixin:A}
	at com.mojang.datafixers.util.Either$Left.map(Either.java:38) ~[datafixerupper-5.0.28.jar%23121!/:?] {}
	at net.minecraft.server.level.ChunkMap.lambda$scheduleChunkGeneration$27(ChunkMap.java:619) ~[client-1.19.2-20220805.130853-srg.jar%23561!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:modernfix-common.mixins.json:bugfix.paper_chunk_patches.ChunkMapMixin,pl:mixin:APP:modernfix-forge.mixins.json:bugfix.chunk_deadlock.ChunkMapLoadMixin,pl:mixin:APP:canary.mixins.json:world.player_chunk_tick.ChunkMapMixin,pl:mixin:APP:railways.mixins.json:ChunkMapAccessor,pl:mixin:APP:ftbchunks-common.mixins.json:ChunkMapMixin,pl:mixin:APP:railways-common.mixins.json:conductor_possession.ChunkMapMixin,pl:mixin:A}
	at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150) ~[?:?] {}
	... 11 more
Caused by: com.mojang.brigadier.exceptions.CommandSyntaxException: Unknown block type 'create:andesite_bricks' at position 0: <--[HERE]

I see, this is a very useful log. Thank you so much for the issue!

Mod versions
create -- 0.5.1.f
create: dynamic village -- 0.2.1

I found the same error
Unknown block type 'create:andesite_bricks' at position 0: <--[HERE]

Should be fixed in newest release :)

authors: GreyMamoN kuolemax sudolev

repo: sudolev/DynamicVillageMod


text:
[FR] 知识库的增量更新

往知识库中导入同名文件的时候，是否有可能实现只更新修改的部分。我想导入我的obsidian笔记，但笔记总是不断更新的，过一段时间知识库中的内容就不是最新的了。

往知识库中导入同名文件的时候，是否有可能实现只更新修改的部分。我想导入我的obsidian笔记，但笔记总是不断更新的，过一段时间知识库中的内容就不是最新的了。

这个目前有难度。首先知识库目前没有存储原始文件，数据存储中只有文件的分块。
针对增量更新，或许我们可以做的是，在导入同名文件时，如果文件已经存在，那么先从向量数据中删除已有数据，再基于新导入的文件再次索引。这样能达到期望效果。

往知识库中导入同名文件的时候，是否有可能实现只更新修改的部分。我想导入我的obsidian笔记，但笔记总是不断更新的，过一段时间知识库中的内容就不是最新的了。

这个目前有难度。首先知识库目前没有存储原始文件，数据存储中只有文件的分块。
针对增量更新，或许我们可以做的是，在导入同名文件时，如果文件已经存在，那么先从向量数据中删除已有数据，再基于新导入的文件再次索引。这样能达到期望效果。

大佬看看这个会不会有帮助？
Chroma
Updating data in a collection
Milvus
Upsert data in partitions

往知识库中导入同名文件的时候，是否有可能实现只更新修改的部分。我想导入我的obsidian笔记，但笔记总是不断更新的，过一段时间知识库中的内容就不是最新的了。

这个目前有难度。首先知识库目前没有存储原始文件，数据存储中只有文件的分块。
针对增量更新，或许我们可以做的是，在导入同名文件时，如果文件已经存在，那么先从向量数据中删除已有数据，再基于新导入的文件再次索引。这样能达到期望效果。

我觉得这样可以了，毕竟重新嵌入的耗时可以接受

authors: meokey sugarforever wwjCMP

repo: sugarforever/chat-ollama


text:
Implement landing page

Reference the Figma Designs - SDR Home 1 and the current landing page for the application landing page layout and content.
Outstanding questions:

Where does search go? Searchworks? Argo?
Do we have designs/content for:

Learn more - the current link goes to https://sdr.library.stanford.edu/
Why SDR?

Done when - the application landing page content matches the design and all links/forms are functional. Including any functionality moved over from H2.

@aaron-collier

The Learn more button in the box on the left goes to https://sdr.library.stanford.edu/
The Search box goes to https://searchworks.stanford.edu/?f[building_facet][]=Stanford+Digital+Repository

Also, the design needs an update for the links in the header still. These should be in order from left to right:

"Contact us" -- opens the form we have now under "Help"
"Help" -- goes to https://sdr.library.stanford.edu/documentation
"Why SDR?" -- goes to https://sdr.library.stanford.edu/
"Terms of Deposit" -- opens a modal with the terms like we have now

Thank you for updating @amyehodge

authors: aaron-collier amyehodge

repo: sul-dlss/hungry-hungry-hippo


text:
openwayback: localization doc - high level

Part 1:  high level description of localizations  (probably blocked by #29 and #30)
Below has been split into tickets
Part 2:  which files were touched (#29)
Part 3:  specific changes for each localized file (#30)
Part 4:  where in updated code these changes would go (#31)
Part 5:  how to keep our localizations separate from upstream in maintainable approach (#32)
e.g.

maven plugin for wars?
additional maven for other modules?
non-maven approach?

list of commits that includes all our local ones with the title for the commit:
git log --pretty=format:'%Cred%h%Creset %C(magenta)%ae%Creset -%C(yellow)%d%Creset %s %Cgreen(%ci)%Creset' --abbrev-commit --date=iso 220c12b...HEAD

More or less in README of sul-dlss/swap, and also part of that repo's git history

repo: sul-dlss/openwayback


text:
Fixed sql generation for user roles

informations:

q
a

Fixed tickets
none

Related PRs
none

BC breaks
none

Documentation PR
none

How to reproduce?

authors: danrot wachterjohannes

repo: sulu-io/sulu


text:
Topic API Error 400

{'status': 'FAILED',
'message': 'Request failed with status code 400',
'data': None}

81c1c6b should fix this now - https://inshorts.me/news/topics

Thanks!

repo: sumitkolhe/inshorts-api


text:
🛑 SISTEMA ROYAL-HOLIDAY is down

In b5f4d5c, SISTEMA ROYAL-HOLIDAY (https://www.royalholiday.com.ar/reservas/admin/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SISTEMA ROYAL-HOLIDAY is back up in 40a0bc9.


text:
Caching User Avatar from githubusercontent

Need Following Tasks:

Download user Github avatar when user just registered;
Modify UserPresenter's gravatar method to using Qiniu CDN image resizing function: https://github.com/summerblue/phphub/blob/master/app/Phphub/Presenters/UserPresenter.php#L11-L16
Add a update avatar button when using editing profile.

Finished

authors: NauxLiu summerblue

repo: summerblue/phphub


text:
Team name

Let's talk about our team name.

@Samualkrish suggested "Pirates".

Infinity
AlphaDogs
Wolverine
LightSaber
Spock
DeeperLearning

AlphaDogs looks interesting. It follows recent news.

I am also going to support "AlphaDogs" :)

Decided. We are AlphaDogs!

authors: Samualkrish mytony summerlight

repo: summerlight/anlp


text:
在编辑器里点击保存，heading的颜色消失

复制过去微信公众号一切正常，但是一点击保存，heading的样式就会变，最直接的是颜色没有了。
请问应该怎么整，谢谢

截个图我看一下，这个可能是样式的问题。截一下obsidian中的效果和微信编缉器里的效果。

我今天复现了，应该是近期公众号编辑器更新引起的。。。等新版吧。

repo: sunbooshi/note-to-mp


text:
如何进行注入操作的

demo里没有如何注入到netcore里的，怎么操作啊？

services.AddScoped(SqlSugarFactory.CreateSqlSugarClient);
public static class SqlSugarFactory
  {
    public static ISqlSugarClient CreateSqlSugarClient(IServiceProvider serviceProvider)
    {
      var configuration = serviceProvider.GetRequiredService<IConfiguration>();
      var connectionString = configuration.GetConnectionString("SmartDbContext");
      var db = new SqlSugarClient(new ConnectionConfig()
      {
        ConnectionString = connectionString,
        DbType = DbType.SqlServer, //必填（那个数据库）
        IsAutoCloseConnection = true, //默认false（是否自动关闭连接）
        InitKeyType = InitKeyType.Attribute
      });  //默认SystemTable
      return db;
    }
  }`

全局过滤器设置呢？就是针对数据库又或者是所有sqlsugar的所有查询操作的？例如我查询所有的数据都会带一个isdeleted=0这个软删除的操作

全局过滤器设置呢？就是针对数据库又或者是所有sqlsugar的所有查询操作的？例如我查询所有的数据都会带一个isdeleted=0这个软删除的操作

我用EF或EF core可以很方便的实现

http://www.codeisbug.com/Home/Doc?typeId=1205

authors: gxlqssjf neozhu sunkaixuan

repo: sunkaixuan/SqlSugar


text:
M2 安装报错

您好，M2芯片 执行sudo wechattweak-cli install 后报错
sudo wechattweak-cli install ------ Download ------ ------ Unzip ------ Execute command: rm -rf /Applications/WeChat.app/Contents/MacOS/WeChatTweak.framework; unzip /tmp/WeChatTweak.zip -d /Applications/WeChat.app/Contents/MacOS Install failed: Execute command: rm -rf /Applications/WeChat.app/Contents/MacOS/WeChatTweak.framework; unzip /tmp/WeChatTweak.zip -d /Applications/WeChat.app/Contents/MacOS failed: {     NSAppleScriptErrorAppName = "wechattweak-cli";     NSAppleScriptErrorBriefMessage = "checkdir error:  cannot create /Applications/WeChat.app/Contents/MacOS/WeChatTwea                 unable to process WeChatTweak.framework/Versions/A/Resources/Base.lproj/TweakPreferencesController.nib                 unable to process WeChatTweak.framework/Versions/A/Resources/Base.lproj/TweakPreferencesController.nib                 unable to process WeChatTweak.framework/Versions/A/Resources/Base.lproj/TweakPreferencesController.nib                 unable to process WeChatTweak.framework/Versions/A/Resources/en.lproj/TweakPreferencesController.strin                 unable to process WeChatTweak.framework/Versions/A/Resources/zh-Hans.lproj/TweakPreferencesController.                 unable to process WeChatTweak.framework/Versions/A/Resources/zh-Hant.lproj/TweakPreferencesController.                 unable to process WeChatTweak.framework/WeChatTweak.";WeChatTweak.framework     NSAppleScriptErrorMessage = "checkdir error:  cannot create /Applications/WeChat.app/Contents/MacOS/WeChatTweak.fra                 unable to process WeChatTweak.framework/Versions/A/Resources/Base.lproj/TweakPreferencesController.nib                 unable to process WeChatTweak.framework/Versions/A/Resources/Base.lproj/TweakPreferencesController.nib                 unable to process WeChatTweak.framework/Versions/A/Resources/Base.lproj/TweakPreferencesController.nib                 unable to process WeChatTweak.framework/Versions/A/Resources/en.lproj/TweakPreferencesController.strin                 unable to process WeChatTweak.framework/Versions/A/Resources/zh-Hans.lproj/TweakPreferencesController.                 unable to process WeChatTweak.framework/Versions/A/Resources/zh-Hant.lproj/TweakPreferencesController.                 unable to process WeChatTweak.framework/WeChatTweak.";WeChatTweak.framework     NSAppleScriptErrorNumber = 2;     NSAppleScriptErrorRange = "NSRange: {0, 157}"; }

解决了，给终端完全访问磁盘权限就行

repo: sunnyyoung/WeChatTweak-macOS


text:
explain

https://github.com/sunscrapers/djoser/blob/f3fc9110947af2afbd8325a1ac4350f0fa8a4908/djoser/conf.py#L139
I'm a bit unclear on the context, but it sounds like you're trying to retrieve setting names from the object itself (self) rather than from the overridden settings dictionary.
can someone exaplain that please

I wasn't here when it was created and it looks weird indeed, but after looking deeper into it I think it's brilliant.
https://github.com/sunscrapers/djoser/blob/f3fc9110947af2afbd8325a1ac4350f0fa8a4908/djoser/conf.py#L121-L124
This allows us to obtain the settings either from django settings, or whenever they are updated (override_settings decorator etc) using the signal. It's just a dict.
https://github.com/sunscrapers/djoser/blob/f3fc9110947af2afbd8325a1ac4350f0fa8a4908/djoser/conf.py#L139
I assume this case you're asking about is important only on update (whenever the signal is fired up), as this allows us to update the dictionary that's already set on self.
In the next line, it updates the existing dict (value) with these new values.
https://github.com/sunscrapers/djoser/blob/f3fc9110947af2afbd8325a1ac4350f0fa8a4908/djoser/conf.py#L140C17-L140C53
This allows us to import Djoser settings directly and use it within the Djoser project.
https://github.com/search?q=repo%3Asunscrapers%2Fdjoser+"+settings."+path%3A*.py&type=code
Here, settings, is literally the instance of this Settings class, with attributes set with setattr onto it.
DRF uses a similar approach. See https://github.com/encode/django-rest-framework/blob/1db19f4b2d1500894448634852e02f73043382e4/rest_framework/settings.py#L197-L198

repo: sunscrapers/djoser


text:
Add icon and apply WordPress formatting

Other than the other links on the Rubik's P2, this custom link does not contain an icon. This PR adds an icon for consistency reasons.
Screenshots

Before:

After:

Hey @nielslange! Thanks for the PR! It seems that your editor has automatically applied your default prettier configuration and, as such, changed the entire formatting of the code. Since this is not really an A8C repo, I'd like if possible to still keep using my own preferred formatting. 🙏
Regarding the icon, that's a good idea to add one for consistency! I think the chevron is often associated with a collapsible and expandable section. I'm thinking perhaps we find a different icon? Maybe the classical skip icon used for music or something among those lines?

authors: nielslange sunyatasattva


text:
feat: add db lint fail-on flag

What kind of change does this PR introduce?
Feature: Adds a --fail-on flag to the db lint command in the Supabase CLI.
What is the current behavior?
Currently, db lint does not provide an option to exit with a non-zero status code on lint errors, limiting its use in CI/CD pipelines.
See: #1812
What is the new behavior?
Introduces a --fail-on flag with options (error, warning, none) to control the exit status of db lint based on lint results.
How has this been tested?
Tested by running db lint with different --fail-on options to ensure correct exit statuses are returned.

Pull Request Test Coverage Report for Build 10776683068
Details

10 of 11 (90.91%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 60.058%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/db.go
1
2
50.0%

Totals

Change from base Build 10699758747:
0.04%

Covered Lines:
6371

Relevant Lines:
10608

💛  - Coveralls

authors: avallete coveralls

repo: supabase/cli


text:
chore: Bump studio to the latest image version 20241014

Bumps Studio to the latest version.

Pull Request Test Coverage Report for Build 11326890211
Details

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 60.211%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
5
12.9%

Totals

Change from base Build 11324872468:
-0.03%

Covered Lines:
6516

Relevant Lines:
10822

💛  - Coveralls

authors: coveralls ivasilov


text:
User already signed up is throwing a wrong message and supabase.io panel not being respected

Bug report
Describe the bug
Even with the "Enable email confirmations" option disabled, I am receiving the message "Thanks for registering, now check your email to complete the process." when I try to signup a user already registered. I don't remember exactly the message, but before this bug start, I was receiving some messages like User already been registered when trying to re-signup an already created user.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Disable Email confirmations on Supabase.io
Try to register an already registered user
See throwing with the wrong message

Expected behavior
When trying to register an already registered user, the message should be consistent and in sync with supabase.io rules of Authentication.
System information

OS: MacOS
Version of supabase-js: 1.23.1
Version of Node.js: v12.13.0

Additional context
This issue breaks my app for 2 days once this messaging flow is the way that I can ensure that a user exists or not in Supabase User Base.

Seems like this has been resolved by #237  am going to close this for now but feel free to re-open if you are still facing issues.
Thanks!

repo: supabase/gotrue


text:
When a user email address is updated, a new account is created to same provider

Chore
A registered user via Github Auth, updates the email address.
Describe the chore
A registered and authenticated user via Github Auth updates its email address. And the change is made with success.
Then when it logouts. And sign in again via Github. It is created a new user.
The database has now two users from the same provider.
Additional context
Steps to reproduce:

I'm using vercel/nextjs-subscription-payments as starting point.
Connect it to Supabase.io
Sign in with Github, Then we make a update email request using:

try {
    const updates = {
        email: email
    }
    const { error, data } = await auth.api.updateUser(session.access_token, updates);

    if (error) {
        throw error
    }
} catch (error) {
    alert(error.message)
}

Then supabase.io sends a email change confirmation to the new user email address

we use the provided token, and send an email update request:

try {
  const updates = {
    email: email,
    email_change_token: changeEmailToken
  }
  const { error, data } = await auth.api.updateUser(session.access_token, updates);

  if (error) {
    throw error
  }
}

supabase.io responds with a success (200) and the email is successfully updated
Logout the user
Sign in again with Github
A new account is created

Took a look at the /PUT user endpoint recently and had some thoughts on this issue:
Constraints

If the user initially signs up via Github, the user should still be able to sign into the same account via Github even if the user changes his/her email.
Since gotrue treats email as identity, changing the email would remove the association between Github and the app account created, which results in a subsequent sign-in with Github creating a new account.
From my POV, a user would only want to change the email address if they want the app notifications to be sent to a different email address.

Solution 1: We do not allow users to update their email if they chose to sign up via an external oauth provider like Github.
Solution 2: We can create a key in the UserMetaData column called "primary_email" for all users which will be the same as the email address they used to sign up. If a user who signed up via an external provider tries to update their email, the "primary_email" in UserMetaData will be updated instead of the Email field used as identity.

Hey @kangmingtay, can I work on this for my first contribution?

Hey @bariqhibat,
Sorry for the delayed reply on this. Feel free to take up the issue if you're still interested.
Thanks!
Joel

Hi @J0,
Has this not been resolved yet? If so then I can start looking into it, bear with me since it's been a while since I've taken a look into the repo. Can assign me on this! Thanks!

@bariqhibat correct me if im wrong but i think this issue has been fixed already, we don't really treat email as identity for oauth logins, we use the oauth provider id returned instead. This means that even if you update your email on github, the oauth provider id doesn't change so a new user wouldn't be created.

Hey @kangmingtay ,
Sounds good, shall we go ahead and close the issue?
Hey @bariqhibat,
Seens like I'm not quite up to date on this issue 😅  Feel free to let us know if the issue still persists for you or if there are any other issues that you'd like to take up.
Thanks!

authors: J0 bariqhibat kangmingtay vmiguellima


text:
Filter composition with and/or/not

What kind of change does this PR introduce?
Adds composition to filters by combining with AND/OR/NOT
Tasks:

[x] add to schema
[x] add to filter builder structs
[ ] update filter parser
[ ] update transpiler

resolves #87

@olirice if you don't mind I would like to take a stab at this. I have initial code in my branch working with AND and OR filters. Just NOT filter is pending.

awesome! yes, pls do. I'll close this PR

authors: imor olirice


text:
Timeout was reached error with incorrect status: SUCCESS

Bug report

Run supabase/postgres docker
Run sql

CREATE EXTENSION IF NOT EXISTS pg_net;
select
    net.http_post(
        url:='https://httpbin.org/post',
        body:='{"hello": "world"}'::jsonb
    );

select
  *
from
  net.http_collect_response(1);

@see

pg_net: Timeout was reached - Watch Video

Notice how the status says SUCCESS, but upon inspecting the net._http_response table, it says timeout was reached. Additionally it appears that the request was never made according to the remote server.

Thanks for the report. Note that there's a timeout(by default 2 seconds) you can add to the function.
select
    net.http_post(
        url:='https://httpbin.org/post',
        body:='{"hello": "world"}'::jsonb,
        timeout_milliseconds := 5000
    );

The SUCCESS is indeed a mistake.

I see. What's the default timeout on supabase itself? Or is it simply faster on supabase and therefore within the 2000ms timeframe?

Default it's the same - 2 seconds.

Or is it simply faster on supabase and therefore within the 2000ms timeframe?

Yeah, latency might be lower due to network proximity.

http_collect_response was made a private function on https://github.com/supabase/pg_net/pull/81.
For now it's better to inspect net._http_response directly. We're going to improve this on https://github.com/supabase/pg_net/issues/62.

authors: steve-chavez tonyxiao


text:
Fix crash in aws sdk

We have seen some crashes because of this issue in the aws-sdk.
I have been able to reliably reproduce this issue using this script in an EC2 server running ubuntu. I am not able to reproduce it locally on my Mac though.

IssueHunt Summary

Backers (Total: $300.00)

 supabase ($300.00)

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

This issue was caused by code reentrant in Node.js http parser, this PR (https://github.com/nodejs/node/pull/43369) is in progress to fix this issue.

Upstream node.js has fixed this issue in https://github.com/nodejs/node/pull/43369, should we follow it up?

Closed via #167.

authors: bnjmnt4n burmecia inian

repo: supabase/storage-api


text:
feat: add gravity support for imgproxy

What kind of change does this PR introduce?
feat: add gravity param support for imgproxy transformation feature
Additional context
https://github.com/supabase/api-gateway/pull/352
https://imgproxy.net/blog/perfect-cut-smart-image-resizing-with-imgproxy/

Pull Request Test Coverage Report for Build 7091088148

42 of 47 (89.36%)  changed or added relevant lines in 2 files are covered.
34 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 84.146%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/storage/renderer/image.ts
41
46
89.13%

Files with Coverage Reduction
New Missed Lines
%

src/storage/renderer/image.ts
34
79.46%

Totals

Change from base Build 7031108426:
0.0%

Covered Lines:
7564

Relevant Lines:
8918

💛  - Coveralls

hey @fenos , we also need this one right?
https://github.com/supabase/api-gateway/pull/352

authors: coveralls egor-romanov

repo: supabase/storage


text:
Ability to query available disk space

Problem
Indexing a vector column can outgrow available disk space.
Proposal
Expose a function that can query available disk space. Later create a wrapper CREATE INDEX statement that aborts it if the available space is not enough.
Prior art

https://github.com/greenplum-db/diskquota
https://github.com/hlinnaka/pg_quota

To not depend on a table (thus on a CREATE EXTENSION supautils) to get this info, we can store it as a PGC_INTERNAL GUC. So the interface to get this info would be:
select current_setting('supautils.free_disk_space', true);

Steps for implementation:

Get the data_directory from pg
Use https://man7.org/linux/man-pages/man3/statvfs.3.html to get free space.
Store it on supautils.free_disk_space.

Sure, we can track those here.

The number of cpus is one function call https://linux.die.net/man/3/get_nprocs.
Total memory can be obtained with https://linux.die.net/man/2/sysinfo.

Was this ever implemented?

bump @steve-chavez ^

This was done only for the case of constrained extensions, which was the immediate use case: https://github.com/supabase/supautils#constrained-extensions (see disk)
The code for getting disk space is there but not sure if we should add SQL objects to supautils since it would make it harder to upgrade (we'd need migrations). Right now it only works with db settings (GUCs).
@burggraf What's the use case you had in mind?

We can implement any resource constraints through config options, but we'd need specific use cases.
As we've had issues with the removed supautils stdlib when doing migrations, I don't think we should add database objects for any functionality.
I've added a clarification for this at the intro of supautils: https://github.com/supabase/supautils#supautils
Will close.

authors: burggraf olirice steve-chavez

repo: supabase/supautils


text:
HTML Parse Error on database migration

I installed a new version of Craft on a staging server and imported my SQL database in from my .dev local environment (where PMM is working great). Now when I try loading a page I'm getting this error:
Parse error: syntax error, unexpected '[' in /var/www/html/craft/plugins/pimpmymatrix/services/PimpMyMatrixService.php on line 142
I'm guessing this had to be because of a database issue, because it asked me to update my database immediately when I went to the Craft Control Panel on the new server after I cloned all the necessary files and imported the database. Any ideas on how to start fresh with PMM? Are there certain DB tables I need to reset and/or delete?

Hmm weird. I'm not totally sure I understand what exactly is going on here but all the tables you need to hunt down are as follows:

craft_plugins - remove the PMM row
craft_pimpmymatrix* - remove any tables that start with this
craft_migrations - remove the rows that mention PMM

Let me know how that goes!

Hey @tyler-deboer any luck with this? Can I close the issue?

I think so yeah! Cleared all the related tables/rows from the database, reinstalled, and everything worked great. Not sure what happened on the migration but it must have been something on my end. Thanks!

No worries, glad you got it sorted :)

authors: joshangell tyler-deboer

repo: supercool/Pimp-My-Matrix


text:
Dashboard Token Listing: TREE

Discord Handle of Submitter: nezz9461
Token Symbol: TREE
Network: Base
Token Address: 0x65e9B4Ae7885BD3E4e1CC4f280863b859d231FC2
Network Explorer Link: https://basescan.org/address/0x65e9B4Ae7885BD3E4e1CC4f280863b859d231FC2
Is a Super Token? true
Address of Underlying Token:  0x6888c2409D48222E2CB738eB5a805A522a96CE80
SVG Logo Link: https://imgur.com/UEilIbS
Coingecko or Hardcoded Price?: Coingecko
Coingecko ID: treeplanting
Harcoded Price (if Coingecko ID is unavailable):
Token HEX Color: #7AA229
Info on Listing: Farcaster community, want to use supertokens to rent adland ad spaces in their own native currency: https://warpcast.com/~/channel/treeplanting
Please close only after token has been added to resolver!

listing done: https://console.superfluid.finance/base-mainnet/supertokens/0x65e9B4Ae7885BD3E4e1CC4f280863b859d231FC2?tab=streams

repo: superfluid-finance/assets


text:
Tweak verbiage for launch

This commit tweaks some of the page verbiage for form notices and
the <h1> for type-os

lgtm

authors: briansage gopherstein

repo: supergiant/supergiant-alpha-signup