text:
ember-simple-auth-devise doesn't add token header

I really don't know if this is a bug, but it drives me crazy. I'm trying to add ember-simple-auth with ember-simple-auth-devise to my application. All works fine, authentication, login, tokens are written to localStorage, but authorization doesn't work: the token header isn't set.
I'm using Ember 1.8.1, Ember Data 1.0.0-beta.12, Handlebars 1.3.0, jQuery 1.11.1, Ember Simple Auth 0.7.2 and Ember Simple Auth Devise 0.7.2 for my frontend. My backend is backed with Rails, Grape and Devise.
Both ember-simple-auth and ember-simple-auth-devise are added to my package.json/bower.json and installed (otherwise authentication/login wouldn't work :smile_cat:) and the authorizer is set in my environment.js file:
ENV['simple-auth'] = {
  authorizer: 'simple-auth-authorizer:devise'
};

I just played around with some console.log debugging. It seems that the authorize function don't get fired. All other functions could be logged successfully, except authorize and I can't figure out why.
I opened a question on stackoverflow too, if this isn't a bug and just a mistake of mine.

I have had this exactly same problem. Although I configured crossOriginWhitelist and it still does not work. I have tried everything I could but not able to make this work.
Using Ember 1.13, Ember Data 1.13, ember-cli 1.13, ember-cli-simple-auth 0.8, ember-cli-simple-auth-devise 0.8 and bundled versions of ActiveModelAdapter (now separate from ember-data) 1.13

@henriquecf I had the same problem, in my case, the issue was in my SessionsController. Make sure your response after creating a session looks like this.
def create
  super do |user|
    data = {
      token:      user.authentication_token,
      email: user.email
    }
    render json: data, status: 201 and return
  end
end

The issue was that I was returning user_email instead of email.

I have even decided to use Oauth after all the problems I have had, but I will try this @holamendi thanks!!

authors: gopeter henriquecf holamendi

repo: simplabs/ember-simple-auth


text:
Add SimpleInjectorAddOptions.ServiceScopeFactory property

Internally, the SimpleInjectorAddOptions class contains a ServiceScopeFactory property that pulls in (and caches) the IServiceScopeFactory from the root MS.DI container (the ApplicationServices). This is used internally to register the IServiceScope.
It can be useful to make this property public. This simplifies the Blazor integration, because it needs an alternative way to register IServiceScope.

feature-18 branch created.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Feedback from devs and OSS tool teams for 'A devs guide to...'

Here is where devs and OSS tool teams can add feedback for the microsite https://simplysecure.github.io/devs-guide-to/. Please add you feedback in a comment so that all feedback is collected in a single place ready to be read, understood, discussed and triaged by the 'devs guide to...' team.

Please add your feedback in an individual comment on this issue. You'll need to be logged into a Github account in order to offer feedback and you can edit comments after you've posted. Our guiding questions are:

What topics or sections were most useful? Why?
How could the resource microsite be improved (content or design)?
What was confusing or hard to understand?
What guides or resources would you like to see added?

Looks great overall, thanks much for sharing it and soliciting feedback. I liked the "Five Whys" approach, definitely something I can see myself using in practice.
Structural feedback: I was a bit confused by the navigational bar at the top vs. the blog section on https://simplysecure.github.io/devs-guide-to/ , i.e. I found myself wondering how the blog and the guide content relate to each other. Perhaps headlines or other ways of separating "news" content from "guide" content could make that distinction clearer.

hi @eloquence , thank you so much for the feedback! It's really great to hear. Your structural feedback is very helpful - we definitely want to avoid confusion and I think other people have the same issue. We'll make some changes to that.

I think this is a great project idea with very important resources for developers. Few things that came to mind while going through the website I will try to note below:

I think the user testing topics are really helpful. I think user testing is a super important part of development which often is ignored, so definitely good resources. I think it might also be useful to add resources about how to draw conclusions from user testing for better development, or what are the methods they can verify that the new solution after user testing is better than the old one.
I think another resource that might be helpful for future along the same veins is "A devs guide to interacting (or collaborating) with designers".
I love the design of the website, but I think there are certain accessibility issues that I noticed. A thorough accessibility audit of the website might be helpful. I know that the website is currently just using a theme, so improving accessibility might mean modifying the theme (or overriding the theme) a bit, but might be worth it.
I agree with @eloquence that I was a bit confused about the structuring and browsing the different articles. The navigation bar is kind of a mix of article listing and navigation, which can be a little confusing. So better article listing/grouping might make it easier to follow.

I echo the points @eloquence and @SaptakS have raised above, re: navigation/structure confusion, accessibility and additional resource ideas.
Some additional thoughts/elaboration I have:

On accessibility: the colours are hard to read for me, especially the colour of the post metadata agains the background (not enough contrast). Also, the body text font is hard to read, especially on mobile. I tried to review the site mostly on mobile (on a small iPhone) but found it too tiring/overwhelming to read and understand. I'd prefer a simpler sans serif font, which would still go with the tech theme/aesthetic but be more accessible.

Alignment: the content's far left alignment is throwing me off on desktop, especially on a large monitor. There's almost 60% of negative space on the right, and my brain would prefer the content to be horizontally centered.

Button UI: I'd appreciate it if the buttons ("read more") were a box/pill ie more elevated from the background, not just text with an arrow

Organizing post content more visually: As someone with ADHD, I'm having a hard time following the paragraphs/lists of text in each post. The images, emojis and headings help, but overall the body text is still hard to follow. I'd appreciate having more differences in font size for headings, maybe a different background colour for quote blocks (if the theme permits), and (if you have capacity) a more visual summary/overview (with post its? a mind map of sorts?) at the top of each post for the very long posts.

Post titles: I appreciate that some titles clearly show what the post is about ... I'd love to see that in every title. Currently, the titles "Imakefoss Twitter takeover" and "Resource #2" don't tell me much about the content, and I have to read the blurb to understand.

Small typo: In the website header, should it be "a dev's guide" with an apostrophe?

What topics or sections were most useful? Why?

I really like the "recruiting testers" piece, which was a bit surprising for me. However, I think, given the difficulty at getting people to participate in anything outside of the normal routing these days, this feels very important. I think the tone of the example messages was well done, and having more of these for different styles of engagements would be great.
I also felt that the detail on the actual mechanics of how to conduct an effective user test was very helpful and useful. Actually setting up an environment that is conducive to documenting a user's typical interactions and habits is difficult. Having more resources related to the sample scripts seems like a good place to focus.

How could the resource microsite be improved (content or design)?

High level, I agree with some of the accessibility and readability concerns. I appreciate the attempt at having a style or look for the site, but having it fit more in with boring "developer documentation" may end up giving it more weight and authority. It feels like too much narrative text covering somewhat obvious points... I found myself skimming a lot of that since it was also a bit hard to read. Once it gets into specific tactics and examples, it feels more useful.

What was confusing or hard to understand?

Nothing was confusing or that difficult to understand. I found myself least interested in the longer narrative explainer text, and more drawn to the structured samples, five whys, etc.... I understand that user testing is important, but need some help with my game plan!

What guides or resources would you like to see added?

The Synthesis portion of this guide was the most novel for me, and something I need to think on more... perhaps more "what next?" resources, or examples of user testing report outcomes from other projects, could be inspiring and motivating.

authors: Erioldoesdesign SaptakS eloquence kelseysmithdesign n8fr8 yannchwen-horizontal

repo: simplysecure/devs-guide-to


text:
Error user login

Hi !
for login after install, user is not admin@tailadmin.com but -> admin@tailadmin.dev
;)

Thanks for feedback, it fixed.

authors: FlashPapa sinan-aydogan

repo: sinan-aydogan/tailadmin-laravel


text:
Add Deep Learning Papers

https://github.com/terryum/awesome-deep-learning-papers
I believe that there exist classic deep learning papers which are worth reading regardless of their applications. Rather than providing overwhelming amount of papers, I would like to provide a curated list of the classic deep learning papers which can be considered as must-reads in some area.

[x] I have read and understood the contribution guidelines and the instructions for creating a list.
[x] This pull request has a descriptive title.
The list I added

[x] is not a duplicate,
[x] has been around for a few weeks,
[x] only has awesome items with descriptions,
[x] contains the awesome badge on the right side of the list heading,
[x] has an appropriate license,
[x] has contribution guidelines,
[x] has been checked for inconsistent formatting, spelling and grammar, and
[x] has been added at the bottom of the appropriate category.

This is a curated list of deep learning papers. I gathered the list of papers based on number of citations and opinions of deep learning researchers. Please give me feedback if anything need to be changed to be added on the awesome list. Thank you.
Terry

has been around for a few weeks,

Not really, see initial commit which is 13 hours old at the time of writing.
Otherwise, I think an interesting list 👍.
Personally, I would format the entries a bit differently such that the titles stand out a bit more. Perhaps make just the title into links instead of putting [pdf] at the end.
I would also advise to use DOI links (e.g. http://dx.doi.org/...) where those are available. That will save you some headaches to keep the links from rotting. The ArXiv links are also quite stable, so those are equally fine.

Ping me here in a few weeks and I'll reopen ;)

source: gharchive/pull-request

authors: egeerardyn sindresorhus terryum

repo: sindresorhus/awesome


text:
Update dependencies

No plans on merging before next week.
I may turn this into a lint by doing onConversationHeaderUpdate here, then updating the other prs.
WDYT?

Blocked by https://github.com/sindresorhus/refined-github/pull/4116
Blocked by https://github.com/sindresorhus/refined-github/pull/4115

I may turn this into a lint by doing onConversationHeaderUpdate here, then updating the other prs.

👍
I avoided updating the textarea dependencies because they need to be tested a little bit. fit-textarea completely changed mechanism in v3

I avoided updating the textarea dependencies because they need to be tested a little bit. fit-textarea completely changed mechanism in v3

I noticed a bug will open an issue there. (it does not resize when content is changed programmatically)

it does not resize when content is changed programmatically

That can never happen, changing the content programmatically does not trigger any events.

I merged #4116 into this. It's now unblocked

@fregante can do a npm install so we can I dont mess you up with fs events?

@fregante can do a npm install so we can I dont mess you up with fs events?

No worries, just do it. And I'll keep either re-adding or ignoring fsevent diffs 😂

Are we good to merge? I want to finish up the other 2 PR's

repo: sindresorhus/refined-github

license: mit

license_source: bigquery


text:
Added lockfile

Fixes #274

Actually, this doesn't fix the issue since package-lock.json is automatically filtered out by npm pack (and in effect npm publish). There will be no difference to the published package after this patch is applied.
The correct approach, in my opinion, would be for each end user to add their own package-lock.json-file, thus ensuring that they always get the expected dependencies.

Thank you for reply

authors: LinusU kutekat

repo: sindresorhus/xo


text:
Added Profile Page Html and Css

While making a pull request, do remember to give some meaningful comments for the greater good of understanding and collaborating.
Do keep an eye of the reviewing of the PR or comments added after the pull, if any and always be home to my thankfulness for your contribution. :)
Please do not make any changes in the following files without contacting me over mail - coding.ayush@gmail.com, else the PR wouldn't be considered:

LICENSE
Readme.md
contributing.md
code-of-conduct.md
how-to-run.md
package.json, package-lock.json
/model

Added Profile Page HTML and CSS


text:
Sqlsmith: Improve design of context

Some issues with current design:

No interface for context
Ambiguous fields (bound_columns, perhaps it should be GROUP BY columns).
Creating a new local context is still error prone, what if wrong current context is passed?      let current_context = self.new_local_context();
      let factor = self.gen_table_factor_inner();
      self.restore_context(current_context);

Can take inspiration from design of BindContext.

Clarified in develop.md for sqlsmith. Works well enough for now.

repo: singularity-data/risingwave


text:
Build failure with AEM 6.2 and maven 3.5

Hi,
I clone project from GitHub. So I build the project with command
cd aem-react
mvn clean install -PautoInstallPackage
The build is failure.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-gpg-plugin:1.5:sign (sign-artifacts) on project aem-react: Exit code: 1 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
How to fix it?
Thank & regards,
BienHV

You need to skip the gpg signature by added -Dgpg.skip=true

Hi Stemey,
Where I need to added -Dgpg.skip=true ?
Thanks

mvn clean install -PautoInstallPackage -Dgpg.skip=true

authors: hoangbienit stemey

repo: sinnerschrader/aem-react


text:
ImportError: no module named 'touchscreen'

Hi, there seems to be an issue with the touchscreen demo. I'm using the Maixpy IDE and it says that it can't find the touchscreen module.

It also says that board_info isn't callable. I'm using MaixPy 5.0.0

same for me: ImportError: no module named 'touchscreen'
No help yet?

Sorry I didn't close my own issue. I later used the lvgl binary and it worked for me @Createyouraccount-alt

Hello, how did you solve this problem?


text:
PulidFluxInsightFaceLoader AssertionError Fix

Hello guys, i'm opening this "issue" to help people with my same issue, the issue in question is this:
ComfyUI Error Report
Error Details

Node Type: PulidFluxInsightFaceLoader
Exception Type: AssertionError
Exception Message:

Stack Trace
  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 323, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 198, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)

  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-PuLID-Flux-Enhanced\pulidflux.py", line 223, in load_insightface
    model = FaceAnalysis(name="antelopev2", root=INSIGHTFACE_DIR, providers=[provider + 'ExecutionProvider',]) # alternative to buffalo_l
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "C:\AITools\ComfyUI_windows_portable\python_embeded\Lib\site-packages\insightface\app\face_analysis.py", line 43, in __init__
    assert 'detection' in self.models
           ^^^^^^^^^^^^^^^^^^^^^^^^^^

System Information

ComfyUI Version: v0.2.6-9-g6c9dbde
Arguments: ComfyUI\main.py --windows-standalone-build
OS: nt
Python Version: 3.12.7 (tags/v3.12.7:0b05ead, Oct  1 2024, 03:06:41) [MSC v.1941 64 bit (AMD64)]
Embedded Python: true
PyTorch Version: 2.5.1+cu124

Devices

Name: cuda:0 NVIDIA GeForce RTX 3060 Ti : cudaMallocAsync

Type: cuda
VRAM Total: 8589410304
VRAM Free: 1258256896
Torch VRAM Total: 5972688896
Torch VRAM Free: 40880640

Logs
2024-11-03 19:12:29,211 - root - INFO - Total VRAM 8192 MB, total RAM 32682 MB
2024-11-03 19:12:29,211 - root - INFO - pytorch version: 2.5.1+cu124
2024-11-03 19:12:29,213 - root - INFO - Set vram state to: NORMAL_VRAM
2024-11-03 19:12:29,213 - root - INFO - Device: cuda:0 NVIDIA GeForce RTX 3060 Ti : cudaMallocAsync
2024-11-03 19:12:30,420 - root - INFO - Using pytorch cross attention
2024-11-03 19:12:31,982 - root - INFO - [Prompt Server] web root: C:\AITools\ComfyUI_windows_portable\ComfyUI\web
2024-11-03 19:12:33,219 - ComfyUI-CogVideoXWrapper.custom_cogvideox_transformer_3d - INFO - sageattn not found, using sdpa
2024-11-03 19:12:33,232 - ComfyUI-CogVideoXWrapper.cogvideox_fun.transformer_3d - INFO - sageattn not found, using sdpa
2024-11-03 19:12:33,233 - ComfyUI-CogVideoXWrapper.cogvideox_fun.fun_pab_transformer_3d - INFO - sageattn not found, using sdpa
2024-11-03 19:12:34,144 - root - INFO - Total VRAM 8192 MB, total RAM 32682 MB
2024-11-03 19:12:34,144 - root - INFO - pytorch version: 2.5.1+cu124
2024-11-03 19:12:34,145 - root - INFO - Set vram state to: NORMAL_VRAM
2024-11-03 19:12:34,145 - root - INFO - Device: cuda:0 NVIDIA GeForce RTX 3060 Ti : cudaMallocAsync
2024-11-03 19:12:38,654 - root - INFO -
Import times for custom nodes:
2024-11-03 19:12:38,654 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\websocket_image_save.py
2024-11-03 19:12:38,654 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Logic
2024-11-03 19:12:38,654 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-mxToolkit
2024-11-03 19:12:38,654 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_JPS-Nodes
2024-11-03 19:12:38,654 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui-various
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_UltimateSDUpscale
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Custom-Scripts
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Chibi-Nodes
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Frame-Interpolation
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\Derfuu_ComfyUI_ModdedNodes
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-GGUF
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-VideoHelperSuite
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\x-flux-comfyui
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\rgthree-comfy
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-KJNodes
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_Comfyroll_CustomNodes
2024-11-03 19:12:38,655 - root - INFO -    0.0 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui-dream-project
2024-11-03 19:12:38,656 - root - INFO -    0.1 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_controlnet_aux
2024-11-03 19:12:38,656 - root - INFO -    0.1 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-PuLID-Flux-Enhanced
2024-11-03 19:12:38,656 - root - INFO -    0.1 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Long-CLIP
2024-11-03 19:12:38,656 - root - INFO -    0.1 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui-reactor-node
2024-11-03 19:12:38,656 - root - INFO -    0.2 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Impact-Pack
2024-11-03 19:12:38,656 - root - INFO -    0.3 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Florence2
2024-11-03 19:12:38,656 - root - INFO -    0.3 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Manager
2024-11-03 19:12:38,656 - root - INFO -    0.3 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Easy-Use
2024-11-03 19:12:38,656 - root - INFO -    0.4 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui-tensorops
2024-11-03 19:12:38,656 - root - INFO -    0.6 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-CogVideoXWrapper
2024-11-03 19:12:38,656 - root - INFO -    0.6 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_LayerStyle
2024-11-03 19:12:38,656 - root - INFO -    1.4 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-PuLID-Flux
2024-11-03 19:12:38,656 - root - INFO -    1.4 seconds: C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\was-node-suite-comfyui
2024-11-03 19:12:38,656 - root - INFO -
2024-11-03 19:12:38,668 - root - INFO - Starting server

2024-11-03 19:12:38,668 - root - INFO - To see the GUI go to: http://127.0.0.1:8188
2024-11-03 19:12:44,268 - root - INFO - got prompt
2024-11-03 19:12:44,324 - root - INFO - Using pytorch attention in VAE
2024-11-03 19:12:44,326 - root - INFO - Using pytorch attention in VAE
2024-11-03 19:12:52,796 - root - INFO - model weight dtype torch.float8_e4m3fn, manual cast: torch.bfloat16
2024-11-03 19:12:52,797 - root - INFO - model_type FLUX
2024-11-03 19:13:18,643 - root - INFO - Requested to load FluxClipModel_
2024-11-03 19:13:18,644 - root - INFO - Loading 1 new model
2024-11-03 19:13:34,820 - root - INFO - loaded partially 5624.8 5625.01318359375 0
2024-11-03 19:13:44,791 - root - ERROR - !!! Exception during processing !!!
2024-11-03 19:13:44,795 - root - ERROR - Traceback (most recent call last):
  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 323, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 198, in get_output_data
    return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 169, in _map_node_over_list
    process_inputs(input_dict, i)
  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\execution.py", line 158, in process_inputs
    results.append(getattr(obj, func)(**inputs))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\AITools\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-PuLID-Flux-Enhanced\pulidflux.py", line 223, in load_insightface
    model = FaceAnalysis(name="antelopev2", root=INSIGHTFACE_DIR, providers=[provider + 'ExecutionProvider',]) # alternative to buffalo_l
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\AITools\ComfyUI_windows_portable\python_embeded\Lib\site-packages\insightface\app\face_analysis.py", line 43, in __init__
    assert 'detection' in self.models
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError

2024-11-03 19:13:44,797 - root - INFO - Prompt executed in 60.51 seconds

Attached Workflow
Please make sure that workflow does not contain any sensitive information such as API keys or passwords.
Workflow too large. Please manually upload the workflow from local file system.

Additional Context
(Please add any additional context or steps to reproduce the error here)
the fix is pretty "simple" (i reinstalled and updated comfyui many times thinking it was my problem or the installation was wrong, but.. i just needed the correct models), it seems that if you let insightface download the models in automatic, the downloaded models will be wrong or some may be missing, and everything just doesn't work. you need to delete the folder "insightface" inside models and and then put this folder inside: https://huggingface.co/Aitrepreneur/insightface (thanks Aitrepreneur for the files)
and everything will magically work. i don't know why. it just does.
i hope with this many people with my same issue will be happy

This is due to incorrect design of the plugin's decompression logic for insightface files, resulting in two layers of the antelopev2 folder. Simply cut out the inner folder to resolve the issue.

I have exactly the same error message. My Comfyui worked an then, without doing anything (updates, ...) I got this error. Reinstalling comfyUI also didn't help.
But my antelopev2 alredy is in the correct folder. That doesen't solve it for me.

I have exactly the same error message. My Comfyui worked an then, without doing anything (updates, ...) I got this error. Reinstalling comfyUI also didn't help. But my antelopev2 alredy is in the correct folder. That doesen't solve it for me.

:c


text:
IT not getting discount on stargates

For the record, I will have to check the prices when I get home, as IIRC a non-miniaturized orbital fort + gate costs around the ballpark of 180 resources to build. (Also 50kT iron & 32kT germ IIRC)

The IT & ISB discounts do stack in OG stars. That said, it doesn't stack with the AR starbase discount. (I know this because I tested it last Tuesday out of boredom.)
For the record, I don't even have ISB for this race (if that matters).

Pulled up OG stars in new game without any fancy settings and yes, it appears craig-stars is overcharging me for stargates. (The discount appears to be baked in to the unit price, so ISB/miniaturization would stack multiplicatively with it as well.)

repo: sirgwain/craig-stars


text:
ImportError: No module named 'Stemmer'

mldl@ub1604:~/ub16_prj/npglm$ python3 experiment.py
Traceback (most recent call last):
File "experiment.py", line 31, in
from features.dblp.extraction import run as dblp_feature
File "/home/mldl/ub16_prj/npglm/features/dblp/extraction.py", line 1, in
import Stemmer
ImportError: No module named 'Stemmer'

pip install --upgrade pystemmer

it works

authors: loveJasmine sisaman

repo: sisaman/npglm


text:
可以支持查询国内和国外ip时分别指派不同的ip库吗

今天看到这个项目非常惊艳，感谢作者的开源付出
可以支持查询国内和国外ip时分别指派不同的ip库吗，比如国内的走纯真，国外的走GEO2lite

很高兴这个项目能够帮助到你 :)
关于你提到的海内外使用不同 IP 库的需求，由于 “国家” 字段同样是 IP 数据库内容的一部分，不同数据库的信息会存在差异，所以基于任一 IP 数据库做海内外判断都可能有误差。
我的建议是尝试用 hybrid-mode 同时查询两个数据库的信息，并自行实现业务逻辑判断。
请参考相关文档：https://github.com/sjzar/ips/blob/main/docs/config.md#hybrid_mode
示例：
1. 下载 qqwry.dat & GeoLite2 数据库
    ips download qqwry.dat
    ips download GeoLite2-City.mmdb

2. 使用 hybrid-mode 查询 2 个数据库
    ips -i .ips/qqwry.dat -i .ips/GeoLite2-City.mmdb 12.12.12.12 -f '*' -j
    {"items":[{"ip":"12.12.12.12","net":"12.11.140.0/22","data":{"0_country":"美国","0_isp":"AT","1_accuracy_radius":"1000","1_city":"","1_continent":"北美洲","1_country":"美国","1_latitude":"37.751000","1_longitude":"-97.822000","1_province":"","1_registered_country":"美国","1_utcOffset":"America/Chicago"}}]}

    ips -i .ips/qqwry.dat -i .ips/GeoLite2-City.mmdb -f '*'  123.123.123.123 -j
    {"items":[{"ip":"123.123.123.123","net":"123.123.123.0/24","data":{"0_country":"中国","0_isp":"联通","1_accuracy_radius":"1000","1_city":"北京","1_continent":"亚洲","1_country":"中国","1_latitude":"39.911000","1_longitude":"116.395000","1_province":"北京","1_registered_country":"中国","1_utcOffset":"Asia/Shanghai"}}]}

命令中的多个 -i 参数会同时生效，使用 -f '*' 检查所有的数据库字段，第一个数据库的字段以 0_ 作为前缀，第二个数据库的字段以 1_ 作为前缀。
希望可以帮助到你～

也可以打包成两个文件（一个国内一个国外），查的时候指定两个-i即可

authors: 0akarma lifespy sjzar

repo: sjzar/ips


text:
Bitbucket:811 ノートの最小化・復元がWindowsのシステムメニューに準拠していない

そのまんま。

Software: Pe
Version: 0.99.174-0fc8289c209f3aa5337833c0f1cd75129cf2291b
BuildType: Release
Process: 64
Platform: 64
OS: Microsoft Windows NT 10.0.19044.0
CLR: .NET 6.0.4

BitBucket から移植

項目
内容

元課題
#811

起票日時
2022-05-25T00:38:27Z

起票者
sk_0520

0e7eb01f1af9d0e4dde1358f1e259d9fa60a8b03

BitBucket から移植

項目
内容

元コメント
#811 コメント

コメント日時
2022-09-20T23:28:21Z

コメントユーザー
sk_0520

license: WTFPL


text:
➕ Add Dynamic "Last Updated" Functionality to All Legal Pages !

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Hey @sk66641 @aditya-bhaumik
I want to add a "Last Updated: " functionality to the legal pages of the website,
specifically the Privacy Policy, Terms and Conditions.
This functionality will be dynamically adjustable to update monthly and yearly.
Please Refer to the attached image for an example of how the functionality should look

Currently, The Legal Pages Do not have these Updates, Which makes user feel Outdated.

Use Case
Monthly Update for Privacy and Terms Pages:
At the start of a new month, the system automatically updates the date on the Privacy page to reflect the current month and year (e.g., "Last updated: August 2024").
I want to work on this, please assign me.
thankyou
Use Case
.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@aslams2020 sure go ahead


text:
Added Favicon as per issue #4

Fixes #4
I have added the following favicon to the website

@sk66641 please review and merge this pull request

@sk66641 can you please add the gssoc labels as the leaderboard will only accept the pull request if it contains the gssoc labels in it


text:
Uncaught alert: Set the Grammar for the Editor

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Unknown Windows Version
Thrown From: preview-plus package, v1.2.6
Stack Trace
Uncaught alert: Set the Grammar for the Editor
At /C:/Users/catson/.atom/packages/preview-plus/lib/preview-plus.coffee:460

Error
  at Object.<anonymous> (C:\Users\catson\.atom\packages\preview-plus\lib\preview-plus.coffee:7:25)
  at Object.<anonymous> (C:\Users\catson\.atom\packages\preview-plus\lib\preview-plus.coffee:1:1)
  at Module._compile (module.js:428:26)
  at Object.defineProperty.value [as .coffee] (C:\Users\catson\AppData\Local\atom\app-1.0.19\resources\app.asar\src\compile-cache.js:169:21)
  at Module.load (module.js:353:32)
  at Function.Module._load (module.js:308:12)
  at Module.require (module.js:363:17)
  at require (module.js:382:17)
  at Package.module.exports.Package.requireMainModule (C:\Users\catson\AppData\Local\atom\app-1.0.19\resources\app.asar\src\package.js:761:34)
  at C:\Users\catson\AppData\Local\atom\app-1.0.19\resources\app.asar\src\package.js:192:28

Commands
     -0:28.8.0 core:cancel (atom-text-editor.editor.is-focused)
     -0:28.3.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:28.3.0 core:cancel (atom-text-editor.editor.is-focused)
     -0:27.9.0 core:close (atom-text-editor.editor.is-focused)
     -0:20.8.0 command-palette:toggle (atom-text-editor.editor.is-focused)
  4x -0:17.4.0 core:move-down (atom-text-editor.editor.mini.is-focused)
     -0:16.2.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:16.2.0 preview-plus:toggleHTML (atom-text-editor.editor)
     -0:12.6.0 fuzzy-finder:toggle-file-finder (atom-text-editor.editor.is-focused)
  9x -0:10.8.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -0:06.2.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:06.2.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:05.8.0 command-palette:toggle (atom-text-editor.editor.is-focused)
  4x -0:03.2.0 core:move-down (atom-text-editor.editor.mini.is-focused)
     -0:02.4.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:02.4.0 preview-plus:toggleHTML (atom-text-editor.editor)

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "preview-plus": {
    "html": "browser",
    "css": "SCSS",
    "htmlu": true,
    "livePreview": true
  }
}

Installed Packages
# User
atom-slime, v1.7.2
color-picker, v2.0.13
emmet, v2.3.13
preview-plus, v1.2.6

# Dev
No dev packages

preview-plus - is deprecated..Please try pp(https://atom.io/packages/pp)

authors: morozzoff skandasoft

repo: skandasoft/preview-plus


text:
Consisten pin button style

From:

To:

and if mouse hovered:

nice work!


text:
Update documentation to use opt-in typography system

Link to the Page
https://www.skeleton.dev/
Describe the Issue
Opt-in typography is now available and merged in to the dev branch:

https://github.com/skeletonlabs/skeleton/issues/1189

We should now follow our own recommendation and begin migrating our documentation site to utilize the new opt-in styling approach. I'll aim to use find/replace wherever possible, but some level of manual scan and replace will be needed here. Likewise we should verify that components that make use of typography are adjusted or configurable as needed - this may entail included new typography-specific props.
Are you able to create a Pull Request with the fix?
Yes

I've recorded my steps for this migration process.
Tips

Created temporary style like a { @apply text-yellow-500; } to ensure elements stand out during review
Focus on only ONE type of typography element at a time (ex: headings, anchors, etc)
Use find/replace for headings, blockquotes, and similar elements. Just be careful when doing so!
Anchor require manual review, there's just no way around it.
Paragraphs have no styles by default, they utilize whatever base typography is set on <body>

Process
I focused on one type of typography at a time, committing these to a PR before moving to the next set.

[x] Headings
[x] Blockquotes
[x] Code
[x] Pre-formatted
[x] KBD
[x] Insertion / Deletion
[x] Anchors (note: requires manual review)
[x] Verify all code block snippets are updated as needed
[x] Review the blog typography plugin styles (ex: <code>)
[x] Remove any use of .unstyled - kept a few in components for backwards compatibility

Review my PR
You can see this in action via the commit log for updating the Skeleton documentation site. Note how I approach this in individuals passes.

repo: skeletonlabs/skeleton


text:
2.0 JS to CSS Theme integration fails to load any theme

Current Behavior
I followed the guide step for step to update and set up the CSS to JS custom theme, and yet nothing loads (this is the same behavior for when I do the skeleton default theme too)
Expected Behavior
I expect my theme to work as expected, leaving my site exactly how it was before.
Steps To Reproduce

From Skeleton 1.2, have a default project set up using JS typed typescript. (Skeleton project)
Update Skeleton to the latest
Create custom-theme.js in your root folder
Go to tailwind.config.js and update to look like the guide's version.
Go to src/app.html and update  with tag data-theme with value of custom-theme
npm run dev

Link to Reproduction / Stackblitz
No response
More Information
I also tried many other ideas to get it to work, including reproducing the same setup for the skeleton.dev website, as well as just trying with the simple preset theme of skeleton's.
Here are all my config files.
vite.config.js
import { sveltekit } from '@sveltejs/kit/vite';
import { defineConfig } from 'vite';

export default defineConfig({
	plugins: [sveltekit()]
});

tailwind.config.js
import { join } from 'path';
import { myCustomTheme } from './custom-theme';
import { skeleton } from '@skeletonlabs/tw-plugin';
import forms from '@tailwindcss/forms';
import typography from '@tailwindcss/typography';

/** @type {import('tailwindcss').Config} */
module.exports = {
	darkMode: 'class',
	content: [
        '../**/*.{html,js,svelte,ts}',
        join(require.resolve(
            '@skeletonlabs/skeleton'),
            '../**/*.{html,js,svelte,ts}'
        )
    ],
	theme: {
		extend: {},
	},
	plugins: [
        forms,
        typography,
        skeleton({
            themes: {
                preset: [
                    "skeleton"
                ],
                custom: [
                    myCustomTheme
                ]
            }
        })
    ],
}

svelte.config.js
import adapter from '@sveltejs/adapter-auto';
import { vitePreprocess } from '@sveltejs/kit/vite';
import { join, dirname } from 'path';
import { fileURLToPath } from 'url';

const __dirname = dirname(fileURLToPath(import.meta.url));

/** @type {import('@sveltejs/kit').Config} */
const config = {
	// Consult https://github.com/sveltejs/svelte-preprocess
	// for more information about preprocessors
	preprocess: [
		vitePreprocess({
			style: {
				css: {
					postcss: join(__dirname, 'postcss.config.cjs')
				}
			}
		})
	],
	kit: {
		adapter: adapter()
		// https://kit.svelte.dev/docs/configuration#alias
	}
};

export default config;

postcss.config.cjs
const path = require('path');
const tailwindcss = require('tailwindcss');
const autoprefixer = require('autoprefixer');

module.exports = {
	plugins: [tailwindcss(path.resolve(__dirname, './tailwind.config.js')), autoprefixer]
};

custom-theme.js
/** @type {import('@skeletonlabs/tw-plugin').CustomThemeConfig} */
export const myCustomTheme = {
    name: 'deploy-mngr',
    properties: {
		// =~= Theme Properties =~=
		"--theme-font-family-base": "Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji'",
		"--theme-font-family-heading": "Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji'",
		"--theme-font-color-base": "0 0 0",
		"--theme-font-color-dark": "255 255 255",
		"--theme-rounded-base": "24px",
		"--theme-rounded-container": "6px",
		"--theme-border-base": "1px",
		// =~= Theme On-X Colors =~=
		"--on-primary": "0 0 0",
		"--on-secondary": "var(--color-primary-50)",
		"--on-tertiary": "0 0 0",
		"--on-success": "0 0 0",
		"--on-warning": "0 0 0",
		"--on-error": "255 255 255",
		"--on-surface": "var(--color-primary-50)",
		// =~= Theme Colors  =~=
		// primary | #00b315
		"--color-primary-50": "217 244 220", // #d9f4dc
		"--color-primary-100": "204 240 208", // #ccf0d0
		"--color-primary-200": "191 236 197", // #bfecc5
		"--color-primary-300": "153 225 161", // #99e1a1
		"--color-primary-400": "77 202 91", // #4dca5b
		"--color-primary-500": "0 179 21", // #00b315
		"--color-primary-600": "0 161 19", // #00a113
		"--color-primary-700": "0 134 16", // #008610
		"--color-primary-800": "0 107 13", // #006b0d
		"--color-primary-900": "0 88 10", // #00580a
		// secondary | #015b13
		"--color-secondary-50": "217 230 220", // #d9e6dc
		"--color-secondary-100": "204 222 208", // #ccded0
		"--color-secondary-200": "192 214 196", // #c0d6c4
		"--color-secondary-300": "153 189 161", // #99bda1
		"--color-secondary-400": "77 140 90", // #4d8c5a
		"--color-secondary-500": "1 91 19", // #015b13
		"--color-secondary-600": "1 82 17", // #015211
		"--color-secondary-700": "1 68 14", // #01440e
		"--color-secondary-800": "1 55 11", // #01370b
		"--color-secondary-900": "0 45 9", // #002d09
		// tertiary | #65a749
		"--color-tertiary-50": "232 242 228", // #e8f2e4
		"--color-tertiary-100": "224 237 219", // #e0eddb
		"--color-tertiary-200": "217 233 210", // #d9e9d2
		"--color-tertiary-300": "193 220 182", // #c1dcb6
		"--color-tertiary-400": "147 193 128", // #93c180
		"--color-tertiary-500": "101 167 73", // #65a749
		"--color-tertiary-600": "91 150 66", // #5b9642
		"--color-tertiary-700": "76 125 55", // #4c7d37
		"--color-tertiary-800": "61 100 44", // #3d642c
		"--color-tertiary-900": "49 82 36", // #315224
		// success | #17c700
		"--color-success-50": "220 247 217", // #dcf7d9
		"--color-success-100": "209 244 204", // #d1f4cc
		"--color-success-200": "197 241 191", // #c5f1bf
		"--color-success-300": "162 233 153", // #a2e999
		"--color-success-400": "93 216 77", // #5dd84d
		"--color-success-500": "23 199 0", // #17c700
		"--color-success-600": "21 179 0", // #15b300
		"--color-success-700": "17 149 0", // #119500
		"--color-success-800": "14 119 0", // #0e7700
		"--color-success-900": "11 98 0", // #0b6200
		// warning | #d19d00
		"--color-warning-50": "248 240 217", // #f8f0d9
		"--color-warning-100": "246 235 204", // #f6ebcc
		"--color-warning-200": "244 231 191", // #f4e7bf
		"--color-warning-300": "237 216 153", // #edd899
		"--color-warning-400": "223 186 77", // #dfba4d
		"--color-warning-500": "209 157 0", // #d19d00
		"--color-warning-600": "188 141 0", // #bc8d00
		"--color-warning-700": "157 118 0", // #9d7600
		"--color-warning-800": "125 94 0", // #7d5e00
		"--color-warning-900": "102 77 0", // #664d00
		// error | #ad0000
		"--color-error-50": "243 217 217", // #f3d9d9
		"--color-error-100": "239 204 204", // #efcccc
		"--color-error-200": "235 191 191", // #ebbfbf
		"--color-error-300": "222 153 153", // #de9999
		"--color-error-400": "198 77 77", // #c64d4d
		"--color-error-500": "173 0 0", // #ad0000
		"--color-error-600": "156 0 0", // #9c0000
		"--color-error-700": "130 0 0", // #820000
		"--color-error-800": "104 0 0", // #680000
		"--color-error-900": "85 0 0", // #550000
		// surface | #055c00
		"--color-surface-50": "218 231 217", // #dae7d9
		"--color-surface-100": "205 222 204", // #cddecc
		"--color-surface-200": "193 214 191", // #c1d6bf
		"--color-surface-300": "155 190 153", // #9bbe99
		"--color-surface-400": "80 141 77", // #508d4d
		"--color-surface-500": "5 92 0", // #055c00
		"--color-surface-600": "5 83 0", // #055300
		"--color-surface-700": "4 69 0", // #044500
		"--color-surface-800": "3 55 0", // #033700
		"--color-surface-900": "2 45 0", // #022d00

	}
}

src/app.html
<!DOCTYPE html>

		<meta charset="utf-8" />
		<link rel="icon" href="%sveltekit.assets%/favicon.png" />
		<meta name="viewport" content="width=device-width" />
		%sveltekit.head%

%sveltekit.body%

Stuck on working on this project until someone can tell me what I am doing wrong.
(I also removed all imports other than the app.postcss import in my +layout.svelte files and removed my old theme file from 1.2)

2 questions so far:

Considering the (thankfully extensive, thanks for that!) code samples, I assume it's a private project that you can't share?
does your app.postcss include the Tailwind directives?

@traviszuleger @Sarenor
I'll append a couple other things of note from the original post above:

From Skeleton 1.2

Skeleton keeps a regular release cadence, pushing out a new update every 2 weeks. As such, v1.2 is from April, so a number of notable updates have dropped in that time. That may not have any impact on your issue at hand, but wanted to make sure it was statedly clearly here.
Here's the changelog if you would like to monitor changes since then:
https://github.com/skeletonlabs/skeleton/releases?page=4

Update Skeleton to the latest

Did you install the Skeleton Tailwind Plugin as well. This bullet point didn't make that clear. It's now a new standalone package that must be installed using (note the second package):
npm add -D @skeletonlabs/skeleton @skeletonlabs/tw-plugin

does your app.postcss include the Tailwind directives?

I'd also be curious to hear about the status of the the @tailwind directives. If those are present it can result in a project that appears to be unstyled (no theme colors)

What the other two said 😄
I will add that I noticed that your content field in your tailwind.config.js has this '../**/*.{html,js,svelte,ts}',. This doesn't seem intentional and it will load everything outside of your project, which will cause everything to slow down to a halt. You said things aren't "loading" so I'm inclined to say that this is the problem.
Change '../**/*.{html,js,svelte,ts}' to './src/**/*.{html,js,svelte,ts}' instead.

@Sarenor You are correct that it is a private repository, it is a project for my company, so it must remain private. I do not have the tailwind directives, it wasn't required in the 1.2 update (as far as I noticed from the old code I had) and there is nothing in the guides to add this. I assume this is just part of the initial startup template. After adding this, though, I get an error now: EMFILE: too many open files, open 'C:\...\node_modules\js-yaml\lib\schema\json.js'.
@endigo9740 it is still in the development phase, so as I've been developing (on and off) I've either decided to hold off on updating (A mistake on my part) or simply just forgot as I continued development.
@AdrianGonz97 I originally had it at 'src/**/*.{html,js,svelte,ts}' but it wasn't working then either, I then saw inside of the repository for Skeleton (https://github.com/skeletonlabs/skeleton/blob/dev/sites/skeleton.dev/tailwind.config.js) that it had this format, so I was trying to relate it as closely as possible to solve this issue.

1.2 update (as far as I noticed from the old code I had) and there is nothing in the guides to add this.
Just to make sure, we are talking about these migration steps and especially 4) https://github.com/skeletonlabs/skeleton/discussions/1947 on the list?

I assume it's loading tailwind and the plugins correctly now but because it's scanning everything around your project as well, tailwind is opening to many files.
Try turning it back to 'src/**/*.{html,js,svelte,ts}', Skeleton is set up that way because of it's mono repo structure and because the docs page needs to pull in the lib changes :)

@Sarenor no I was referring to what was on the website. I did not know that guide existed. Let me look at that and respond momentarily on if it worked...

@Sarenor @endigo9740 @AdrianGonz97
Thank you, it seems it was a combination of the tailwind directives and that path you mentioned.
As for feedback, it'd be nice if https://skeleton.dev could reference #1947 instead of only referencing bits and pieces, as it isn't  as easy to find guides through the repository.

@traviszuleger I'm not sure I follow. We link to both the release notes AND the migration guide directly on the homepage:

Additionally both posts are pinned on our GitHub Discussions section, and I believe we've reference both in all public announcements on Discord and Twitter.
The release notes themselves also link to the Migration guide as well.
We've tried to be very diligent about our redundancies for accessing this guide. Maybe we missed something?

@endigo9740 As I am sure many people could agree with me, these websites are cached or bookmarked. I no longer first visit the homepage, and that toolbar doesn't show up on any other page. I would have never known about it if you didn't mention it now. That is my fault, but I would then suggest that that toolbar could be on all pages (with an option to dismiss it)

Gotcha, ok we'll keep that advice in mind for the future then! Glad you got things sorted though!


text:
Fix broken error handling specs

The reason the specs are failing is because of the following change
in the webmock gem:
https://github.com/bblimke/webmock/commit/1c48030ec0671e368d5be09f39cdfbed6a87b10f#diff-4fd2506a42939f27882b390651103483
RequestStub:to_timeout method now raises a Net::OpenTimeout exception
instead of a Timeout::Error. The Net::OpenTimeout error when using Faraday
is wrapped in a Faraday::ConnectionFailed error, that is not rescued and re-raised
as a Skroutz::Timeout error: https://github.com/skroutz/skroutz.rb/blob/master/lib/skroutz/errors.rb#L92

Coverage remained the same at 95.075% when pulling 23ddc6f4c621f7a7311d17d44a6c05c3817c8c5f on fix_broken_error_handling_specs into 7345c3cf6f24e6ed69cfa365312298d7814ffa41 on master.

Coverage remained the same at 95.075% when pulling 23ddc6f4c621f7a7311d17d44a6c05c3817c8c5f on fix_broken_error_handling_specs into 7345c3cf6f24e6ed69cfa365312298d7814ffa41 on master.

authors: coveralls harrisred


text:
[ENH] improvements to _check_soft_dependencies

Migrates improvements to _check_soft_dependencies from sktime:

https://github.com/sktime/sktime/pull/3925
https://github.com/sktime/sktime/pull/3955

Codecov Report

Merging #88 (90fa48b) into main (7f9cb98) will decrease coverage by 0.50%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main      #88      +/-   ##
==========================================
- Coverage   59.12%   58.62%   -0.51%
==========================================
  Files          22       22
  Lines        1397     1421      +24
==========================================
+ Hits          826      833       +7
- Misses        571      588      +17

Impacted Files
Coverage Δ

skbase/testing/utils/_dependencies.py
38.38% <33.33%> (-2.95%)
:arrow_down:

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

Also, can we add tests of _check_soft_dependencies?

Sure! Note, there weren't any to start with, and it is not obvious how to ensure the test condition is constant, because it is always using the environment constructed from pyproject.
I can test against that environment (assuming the lower bounds will always stay the same) and some negative cases.

Have added tests.

authors: codecov-commenter fkiraly

repo: sktime/skbase


text:
Notebook 3 - minor fixes in content

Updates some content from feedback by @benHeid here https://github.com/sktime/sktime-tutorial-euroscipy2024/pull/27

@fkiraly this can be merged


text:
Looks broken in Nested Content

Open for suggestions on how it should look in Nested Content.

Just to understand this is when you use the Matryoshka Group Separator in an Nested Content or? :)

Yes :)

IMO there are two possible solutions:
What is your prefered solution? Show a styled separator? Or don't show the separator at all in nested content?

I think a styled seperator probably would be nice.

How about this? Very subtle...

How about this? Very subtle...

Could probably work great with collapsible groups (#3)

Fixed in https://github.com/skttl/our-umbraco-matryoshka/commit/6b2610c738f96fad371297f31def609985364778

authors: AndersBrohus-MySupport EcreoApS FransdeJong skttl

repo: skttl/our-umbraco-matryoshka


text:
Rename Dockerfile to Containerfile and remove the dockerfiles folder

The Dockerfiles in the dockfiles folder point to qpid-dispatch project and are obsolete. The new Dockerfile is here - https://github.com/skupperproject/skupper-router/blob/main/.github/scripts/Dockerfile
Rename the above Dockerfile to Containerfile

What about putting the Dockerfile to the top level folder?

I'm not aware why. I don't see a good reason, I guess @fgiorgetti wanted to tuck it away somewhere.

It can be moved to the top folder. I put it there initially cause the original qpid-dispatch repo already had a Dockerfile
at top level and I wanted to prevent the new one being used as if it was the old one.
But since the original one is gone, it can definitely be moved to top folder and renamed to Containerfile.

authors: fgiorgetti ganeshmurthy jiridanek

repo: skupperproject/skupper-router


text:
Stopped with status

Description
This PR add a new event called DOBBY_CTRL_EVENT_STOPPED_WITH_STATUS. This event has an additional parameter i.e. the return code of the app. This event is fired after DOBBY_CTRL_EVENT_STOPPED event. Client code could choose to subscribe to any of the 2 events. The DobbyProxy is currently still subscribed to the DOBBY_CTRL_EVENT_STOPPED event.

@bgray-sky and @iml04 if you are happy I will merge this PR on my local fork.
After this I can create a new PR for merging to the main repo.

repo: skyadiddee/Dobby


text:
Enable all topology and flow probes by default

Right now, only the 'fabric', 'netlink' and 'netns' topology probes are enabled by default, and no flow probe is enabled by default.

We can remove the probe section for flow in the config file, activating all of them by default. We should just rely on topology.
For the ovssflow we should add a optional parameter for the capture creation allowing to specify the ovsdb endpoint. So that we can use ovssflow for external ovsdb compliant switch.

enabling all flow probes is done. only topology part needs to do.

This was done for the probes where it was possible/made sense.

authors: lebauce masco-enovance safchain

repo: skydive-project/skydive


text:
RF Bridge not recognized

I am running a RF-Bridge 315/433Mhz - model SANTTON_RF-2 which is connected to my account and visible/controlable via the ewelink app. But get_devices doesn't show it. As far as I can see, the main difference between the original Sonoff-RF-Bridge (which is working fine) and this one is the device-id - this model starts with: 1001 wheres all my other sonoff-devices are starting with 1000. Is there any filter on the device list?

Oh sorry, I just found the solution: https://github.com/skydiver/ewelink-api/issues/88#issuecomment-643574472

repo: skydiver/ewelink-api


text:
Making snapshot const?

It would be really great if the Registry's snapshot function could be marked const, but something that gets in the way of that is the following line which gets a view into the registry for a particular component. Since view calls ensure, which is non-const, the Registry member variable of the snapshot class can't be marked const. Do you think there might be a way around this? Would be nice to have, but not particularly important.
https://github.com/skypjack/entt/blob/d1db029690e94dfce701fd5d5c1ecc145e97dac4/src/entt/entity/snapshot.hpp#L137

Do you think there might be a way around this?

I don't think it's a problem. However, a const version must still return a non-const temporary Snapshot<Entity>, so I don't get the reasons behind this request.
Returned value can't be const, mainly because all the member functions of Snapshot<Entity> accept an archive and invoke its operator() somehow. The latter is expected to modify something under the hood, so it cannot be const. Therefore, member functions of Snapshot<Entity> cannot be const.
Because of this, having a const snapshot member function in the registry isn't that useful, for you cannot use it in a constant context anyway.
Did I miss something?

No, wait, maybe you misunderstood me.
I didn't mean it is going to modify the registry, it won't happen. I mean that the Archive::operator() member functions aren't required to be const and probably they won't be so. Mainly because they accept some data and write them somehow, somewhere. If you imagine a stack based archive (like the trivial one used to test the feature), it's quite obvious that those member functions cannot be const (unless you decide to use mutable everywhere).

@nbelakovski Can I ask you for what you're using EnTT? Just out of curiosity.

I work with @dbacchet :)

Yeah, definitely!! :-)
Let me know if it works fine for you and feel free to ping me if you find any other issue.
I'll be out of home until Wednesday. I can take in charge new requests as soon as I'm back.

authors: nbelakovski skypjack

repo: skypjack/entt


text:
Add theme package @kodiak-ui/theme for a default theme

Summary
In order to provide a sample for docs the code template needs to remain small.  Placing the theme externally allows it to be imported in a package which reduces the code size as well as allows for quick setup of projects using kodiak

Main Story: ch62035
:vertical_traffic_light: Acceptance criteria

[x] Theme can be accessed by importing { theme } from '@kodiak-ui/theme'

Implementation Tasks

Deployment
Before merge to master
Note: Code merged to master should be safe to automatically deploy to production as-is.

[ ] [QA] User-testing/quality assurance done

After merge to master

@wesleycole will merge this one since it has no dependencies and will initially be used by the codesandbox docs

repo: skyverge/kodiak-ui


text:
Question: Performance vs a Paper Server.

Would a Quilt Server with these mods or a Paper Server with no plugins be Faster?

In my experience both have pretty similar performance with Paper being maybe a bit faster, but I haven't used Paper in quite a long time. I would recommend testing manually, perhaps with a Spark profile

Thanks

repo: skywardmc/adrenaserver


text:
🛑 Ctear is down

In b725cfc, Ctear (http://ctear.com.ar/) was down:

HTTP code: 500
Response time: 1122 ms

Resolved: Ctear is back up in 738fef1.


text:
Force no layout, cause jekyll supports default ones.

Force a null layout when rendering a page.
Having a default layout for the whole site breaks this and navbar or headers get indexed too.
This ensures we are indexing only the content.

👍

authors: vlsi ys

repo: slashdotdash/jekyll-lunr-js-search