GroundDB is causing an endless re-subscribe loop

If the app loses connection with the server, when it comes back online it continuously tries to refresh it's data with the server. I went back and found out that this issue started happening with version 3.9 once the switch was made to using the dispatch:kernel package. If you refresh the app, this issue goes away and it just connects once.

I've released 2.0.0-alpha.1 Notes about the new version, migration and what it doesn't do - The issue might be resolved in that version, let me know

We tested it today, but the issue is still there.

So do I, just downloaded and installed v2rc4 and all my template level subscriptions are re-subscribing endlessly. @raix any guidance will be very much appreciated. Thanks. i'm using this packages:
meteor-base             # Packages every Meteor app needs to have
mobile-experience       # Packages for a great mobile UX
mongo                   # The database Meteor supports right now
blaze-html-templates    # Compile .html files into Meteor Blaze views
session                 # Client-side reactive dictionary for your app
jquery                  # Helpful client-side library
tracker                 # Meteor's client-side reactive programming library

es5-shim                # ECMAScript 5 compatibility for older browsers.
ecmascript              # Enable ECMAScript2015+ syntax in app code

less
twbs:bootstrap
cwaring:modernizr
revox:pages-core
gromo:jquery.scrollbar
fortawesome:fontawesome
meteorhacks:flow-layout
zimme:active-route
momentjs:moment
kadira:flow-router
softwarerero:accounts-t9n
accounts-base
accounts-password
accounts-ui
aldeed:simple-schema
aldeed:collection2
ejson
useraccounts:flow-routing
kadira:blaze-layout
useraccounts:bootstrap
random
aslagle:reactive-table
anti:i18n
mayankchhabra:autoform-switchery
alanning:roles
aldeed:autoform
aldeed:autoform-bs-datepicker
aldeed:autoform-bs-button-group-input
check
kadira:debug
browser-policy
reactive-var
dburles:google-maps
rajit:bootstrap3-datepicker
<EMAIL_ADDRESS>aldeed:autoform-bs-datetimepicker
gandev:server-eval
oaf:moment-duration-format
rzymek:moment-locale-es
natestrauser:select2
aldeed:autoform-select2
standard-minifier-css
standard-minifier-js
meteorhacks:subs-manager
dbarrett:dropzonejs
rikonor:autoform-image-gallery
leeb:bootstrap3-select
lepozepo:accounting
gibson:meteor-autonumeric
jeremy:selectize
comerc:autoform-selectize
jamiecollinson:selectize-bootstrap
awsp:handsontable
elevatedevdesign:autoform-nouislider
ecwyne:nexmo-sms
cosio55:autoform-cloudinary-es
anti:fake
isotope:isotope
mrt:jquery-masonry
osv:mongo-counter
ground:db

I have the same problem on Android.
I found that having the package, event unused, cause DDP to dis/connect continuously. So the resubscribing is fired endlessly.
If you want a repro:

create a new app with meteor
paste this:

Meteor.startup(()=> {
  Tracker.autorun(()=>{
    console.log(Meteor.status().status);
  });
});

add the grounddb package
launch on the device

is this also happening on 2.0.0-rc.5?
try removing ground db and keep<EMAIL_ADDRESS>to see if the issue persists

Indeed<EMAIL_ADDRESS>alone leads to this issue.

@dagatsoin @raix  I tried with fixed dispatch:Kernel .  No luck It still going in endless loop.
I am having a same problem My page refreshes endlessly.  I tried<EMAIL_ADDRESS>as well as deeeed:grounddb2. Same issue with both.
And I am sure Its the problem of dispatch:kernel . Can you please help me out.

Could you provide a repro ? It could also be related to the code of the subscribe function (I had this case too).

@dagatsoin Hey, Thanks for the reply. I can't share my code due to some reason. Sorry for that. But Can you please let me know something about possible issue. So I can check by myself.


Fix flake8 error

I accidentally broke the build on the original PR, this should fix it

Codecov Report

Merging #2 into replay_file will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           replay_file       #2   +/-   ##
============================================
  Coverage        99.74%   99.74%
============================================
  Files               18       18
  Lines              790      790
============================================
  Hits               788      788
  Misses               2        2

Continue to review full report at Codecov.

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


[DDW-388] Detect if Daedalus was launched using Launcher

This PR implements an error dialog shown in case Daedalus was NOT started using Launcher.exe on Windows platform.
Todo:

[x] Implement platform specific error messages

Screenshots:

Review Checklist:
Basics

[ ] PR is updated to the most recent version of target branch (and there are no conflicts)
[ ] PR has good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[ ] CHANGELOG entry has been added and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance tests are passing (yarn run test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn run dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn run package / CI builds)
[ ] There are no flow errors or warnings (yarn run flow:test)
[ ] There are no lint errors or warnings (yarn run lint)
[ ] Text changes are proofread and approved (Jane Wild)
[ ] There are no missing translations (running yarn run manage:translations produces no changes)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn run storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly documented and commented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-rendering
[ ] Any code that only works in Electron is neatly separated from components

Testing

[ ] New feature / change is covered by acceptance tests
[ ] All existing acceptance tests are still up-to-date
[ ] New feature / change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review:

[ ] Merge PR
[ ] Delete source branch
[ ] Move ticket to done on the Youtrack board

@darko-mijic can you please check the alert dialog content?

Let's change the copy to:
Daedalus improperly started!
Please start Daedalus using the icon in the Windows start menu or using Daedalus icon on your desktop.

MacOS / Linux message:

Windows:

@darko-mijic @cleverca22 @deepfire this PR is now ready for review!

@cleverca22 @deepfire guys please review this one - we need approval from at least one Devops team member. Thanks! 🙏

Alan has tested windows build and confirmed that the fix works as expected. Merging this PR now...


add platform verification, aix ruby 3.0 support

This PR includes three commits:

allow aix to require ruby 3.0 instead of 3.1, until we are able to get a functional ruby 3.1 build on aix.
add logging to the verification pipeline to capture OS name/version so that we can verify that the OS we are testing on matches the one we think we are testing on
add logging to omnibus build and omnibus verification tests for the same

Normally I would split these into two PRs, but this saves us several hours of pipeline runs. The commits are separated so that it will be clear in history.
replaces #13204.

Replaced with #13206, #13207


Added support for AWS IRSA in helm chart

Signed-off-by: Steven Jenkins De Haro<EMAIL_ADDRESS>Adds support for AWS IAM Roles for Service Accounts (IRSA) in the helm chart to the KEDA service account. For example, if podIdentity.irsa.enabled is set true along with the needed config, the below will be rendered:
apiVersion: v1
kind: ServiceAccount
...
  annotations:
    eks.amazonaws.com/audience: "sts.amazonaws.com"
    eks.amazonaws.com/role-arn: "arn:aws:iam::000000000000:role/example-irsa-role"
    eks.amazonaws.com/sts-regional-endpoints: "true"
    eks.amazonaws.com/token-expiration: "3600"
...

Checklist

[ X] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ X] A PR is opened to update KEDA core (repo) (if applicable, ie. when deployment manifests are modified)
[X ] README is updated with new configuration values (if applicable)

Fixes #233

hi, i would need this feature, do you have an estimate of when will it be released?
Thanks!

Same question: when will it be released? Any news?

Next KEDA release will be around Dec 8th, and it includes the chart. You can check the release dates here


[release-v1.9] Add patch Channel tests namespace and images

As per title + make generate

Circular dependency with: https://github.com/openshift-knative/serverless-operator/pull/2069, so merging manually


[KBFS-2574] init: Fix service notification race

Fix race where service notifications could arrive before the MDServer/BlockServer were initialized.

Actually, CI fail. Please hold off review. I reversed the race :(

Oh yeah it works now :)

Oops didn't actually see your comment of "holding off review"; still LGTM!


authenticate assumes all users in one ou, always uses uid attribute

In our ldap, we have a whole tree of different organizations - for example, my dn looks something like this:
cn=andymc,ou=myOrg,ou=New York,ou=US,o=myCo
and other users might be in other countries or states, etc...
It would be great if authenticate could accept a form of username that was just the whole DN, and didn't mess with it at all. If I have time I'll implement it, but not sure how you'd like it done.

There's a way to specify the DN (without the base) in the authenticate function, you can do it like this:
Paddle.authenticate([cn: "andymc", out: "myOrg", ou: "New York", ou: "US", o: "myCo"], "mypasswd")

But you're right, forcing the user to use uid as an identifier isn't standard, that should be configurable, I'll fix it in a moment.
Please contribute to this project if you want to, I'll be happy to explain how this lib works and merge PRs ;-)


Tests fail when run in parallel

Multiple tests are using the same TMPDIR, so running them in parallel with something like
make check-TESTS -j8

will pretty reproducibly fail with an error like
FAIL: heap-profiler_debug_unittest.sh
=====================================

rm: cannot remove '/tmp/heap_profile_info': Directory not empty
mkdir: cannot create directory '/tmp/heap_profile_info': File exists

This affects e.g. Debian package builds, where the tests are run as part of the build process and people want to use parallel compilation for performance reason.
Is there a reason not to use a dedicated TMPDIR for each test?

No reason. Feel free to patch this. Thanks for raising it.


[A11y][Reflow]Some of the information is missed when reflow is applied

Copied from https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1188115
Browser Details:
Firefox Version: 79.0 (64 bit)
OS Details
Microsoft Windows 10 Enterprise
Version 2004 (OS Build 19041.450)
Note:
Under 'Members' Administrator dropdown is not visible clearly after applying reflow
Repro Steps:
Change the Display resolution to 1280*1024 in System display settings
Hit the URL and login with appropriate credentials
Tab till "Open Profile drop down" and press enter
Tab till "Manage organizations" and Press enter
Tab till "Edit " present in any record the table and press enter
Tab till Certificates and expand it
Apply reflow and Check whether data is missing or not

Actual Results:
Some of the data is missing when reflow is applied under the Certificates
Expected Results:
User should be able to view the data without missing and all the information should be visible clearly with one scrollbar after applying reflow
User Impact:
Users will not be able to see the information if it gets overlapped in reflow
Notes
This is referencing the information on the Manage Organization page after setting minimum required CSS width (320 pixel).

The information on this page entirely is difficult to see at the minimum width.

Linked issue is closed.


Change and test symlinking code to not change directories

See: https://github.com/ManageIQ/manageiq-appliance-build/pull/14#discussion_r34285335
It's not a difficult change, but requires some testing... putting this here to remember to do it.

heh. now that appliance_console is merged, we'll see how this all comes together tomorrow

Yeah, chdir is not necessary.  ln doesn't resolve the first parameter...it just uses it directly.


[ISSUE-10875]feat(community): add contributor over time graph to website

Fix #10875
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Hi community!
We're the maintainers of Apache APISIX. To better present how our community grows, we develop a tool to show contributors growing history on https://github.com/api7/contributor-graph. Since we found it helpful, we think maybe if it could help some other community.
(And actually, streamio have already used the graph in the blog)
WHAT IT IS
Basically, it just shows the contributors growth over time. All of the procedures are running on GCP, and it would automatically update the graph each day, so the link would always present the real-time data. There is some other stuff to play around with if you would like to give it a try~

HOW IT WORKS
We use Github API to get all commits, try to find the “Github way” to filter commits so the result data would be similar to Github, and then get the first commit time of each contributor. We also support importing contributors from svn, and aggregating contributors from multiple repos if needed.
Currently I find it might be a good place to place it at https://pulsar.apache.org/en/contributing/. Don't hesitate to tell us if there is a better place to present this graph other than this, or there are some other worries or other features you would like to have~🍻
Verifying this change

[x] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
no
Documentation
no

Some open-source projects can provide professional dashboards to monitor the community growth, performance, contributors, and other useful metrics (for example, Apache Kibble, CNCF - CHAOSS/ Augur, CNFF - CHAOSS/ GrimoireLab, CNCF Devstats). There might no need to add a specific tool in the contributing.md, users can pick up their desired ones to track different metrics.

Good to know that! Thanks!

From my personal point of view, this is an excellent tool that counts the growth of contributors over time and monthly contributors to this project, and I think we should consider merging it @Anonymitaet

@Yiyiyimu Thanks for your comprehension. Hope we two communities can have more cooperation in the future.
@tuteng thanks for your suggestion. Remaining neutral might be a better approach to maintaining a vibrant community.


Rest api new sso

Closing in favor of https://github.com/inveniosoftware/invenio-oauthclient/pull/214


Includes instructions for retired EAC

It looks like the portal instructions are for the old Exchange Admin Center, which has a banner stating "This feature has been retired." The retention policy creation process in the new Compliance Manager is quite different and it's not clear if/how policies made in the retired product carry over to the current one.

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

ID: d2e247ee-12d5-add4-756c-b8a8d4ebb7a3
Version Independent ID: 889ce47a-58f5-7bc1-2343-64dcd4bdac2a
Content: Increase the Recoverable Items quota for mailboxes on hold - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/increase-the-recoverable-quota-for-mailboxes-on-hold.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@faboo First, if you're having issues with the procedures in this topic, please contact Microsoft Support. That said, I'm pretty sure the classic version of the EAC is still available to use to implement the solution outlined in this topic. The underlying PowerShell cmdlets are still available. So suggest you continue to use the classic EAC. I can't explain why the new EAC doesn't let you manage Exchange/MRM retention policies. Also, I'm not sure what "Compliance Manager" in your original message refers to or how it's related to the solution for increasing Recoverable Items quota. I do know that the two key parts of this solution (creating an Exchange/MRM retention tag for the Recoverable Items folder and moving items to the archive mailbox) are not supported by M365 retention policies that are managed in the M365 compliance center. Those limits are described here. So until you can do those two things with M365 retention policies, the solution outlined in this topic is the supported method of increasing recoverable item quota.
I hope this helps.


Mongo indexes unique: 1 is in wrong place

Based on Mongo documentation unique: true should be outside of the key object.
https://github.com/jedireza/aqua/blob/ea085be912494561149e1899d68cb468e5e0d144/server/models/user.js#L203-L206
Proper structure example:
User.indexes = [
     { key: { username: 1 }, unique: true },
     { key: { email: 1 }, unique: true }
 ];

Yep. We need a PR just like https://github.com/jedireza/frame/pull/178

I've decided to archive this project. Thank you for your interest and contributions.
https://github.com/jedireza/aqua#no-longer-maintained


Unbunching using IPT2

Hi,
Thank you very much for the mod and it certainly unlocks the potential of buses in the C:S.
I personally prefer IPT2 over TLM because it allow me to configure where unbunching should occur, most usually at terminus. Unless a route is looped, I would allow unbunching to occur at the two ends of the route, like in real life.
Therefore, I wonder if you can please add a feature to only allow "stop-on-demand" at stops where "vehicle unbunching" is FALSE as defined using IPT2, and to disallow "stop-on-demand" at stops where "vehicle unbunching" is TRUE. In this case, unbunching do not necessarily need to occur at the first stop.
I look forward to seeing this feature in the upcoming update.
Thanks,
Herman

Hi there!
Thanks for your support to this mod!
Indeed, the current way of making new routes in vanilla game makes it look like all routes are looping routes. Currently, I made it so that the first stop is the terminus stop. But, me using TLM, I eventually began to feel that moving the terminus and just re-configuring the route sequence is getting tedious as the route grows. (Unfortunately TLM does not have the option to selectively unbunch at stops...)
I understand that IPT2 also has the option to configure unbunching, and afaik, it is set to be "unbunch here" for all stops, and there is no way to change this.
From a convenience standpoint/personal imagination, it would be best if e.g. I make a new route, disable unbunching at the one/two terminus points through IPT2, invert them all on this side internally when reading the settings, and unbunch accordingly. This involves the least amount of clicks, but will probably work against users like you who have already configured unbunching properly as specified by the IPT2 UI to only unbunch at select stops.
Seeing that I will eventually need to make a separate compatibility mod for actually reading IPT2 unbunching config (this is from technical limitations), I guess I could leave this for that eventual mod.
But still, while we are here, I have some rough ideas on what options to offer to IPT2 users regarding unbunching:

"First Principles": Unbunch at the first and only the first stop of route as seen from the game data
"Respect IPT2 Unbunching": does what it says, unbunch only when IPT2 says to unbunch (will not unbunch in case IPT2 did not specify)
"Invert IPT2 Unbunching": unbunch when IPT2 says NOT to unbunch, and do nothing when IPT2 says to DO unbunching (still will not unbunch in case IPT2 did not specify)

This option will probably be save-based, and there will also be a global setting to fall back to when the city does not have any info on that option.
And, this will require me to lean the techs of mod options page and data storage (which I haven't learned how to do yet) and so no matter how you look at it, it won't be available very soon. There will be time to think about and go over the details.

Definitely looking forward to it. : )

I'm gonna redirect this to the sister repo later: https://github.com/Vectorial1024/ExpressBusServices_IPT2
I decided to stick with a global config because that is way easier than per-city configs, but otherwise the main idea is there.
Later when I have the time to deal with the Workshop upload process then it will be available. Time to do other things...


Move imports to top for nsw_fuel_station

Breaking Change:

Description:
Related issue (if applicable): #27284
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[ ] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Yeah I saw that too. Do you know why it is still failing?

@nickw444 could you please review the changes that I made? :)


[Potential Bug] Render Complete Semaphore is specified using currentFrame rather than imageIndex which can cause sync validation errors.

As title suggests. I noticed this after comparing my work with yours (having previously followed the tutorial before), and having conferred with someone in the Vulkan discord.
The solution would be to create an array of Semaphores and access them using the imageIndex passed back from acquireNextImage, in place of the current renderCompleteSemaphore within the SyncSemaphores record.
You could also do the same by specially accessing the SyncSemaphores array for the render complete semaphore: syncSemaphores[imageIndex].renderCompleteSemaphore().vkSemaphore

Additionally, the index for the LightingFrameBuffer VkFrameBuffers should also be using this same imageIndex, rather than how it currently uses the current frame.

Sounds awesome! I will take a look at it when it's done, although not looking forward to more sync error nightmares. Hopefully it will run faster though :)

I can give access to the working source code if you want to have a look. I'm regulary testing with sync validation layers on.

Sure if you want. Not sure if there's a DM feature here but I guess you could just post it


No 'Rehydration priority' option shows in Update Access Tier dialog when selecting several blob

Storage Explorer Version: 1.16.0-dev
Build: 20200912.3
Branch: main
Platform/OS: Windows 10 / CentOS 7.6.1810 (Core) / MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Expand one storage account -> Blob Containers.
Create a blob container -> Upload two blobs as block blob.
Select the two blobs then right click -> Click 'Change Access Tier...'.
Check whether the 'Rehydration priority' option shows on the 'Update Access Tier' dialog.

Expect Experience:
Display the 'Rehydration priority' option.
Actual Experience:
No 'Rehydration priority' option displays.

More Info:
This issue also reproduces for Blob folders.

Verified 20200916.1. This issue has been fixed. So close it


feat: add Together AI integration and provider implementation guide

Related issue: #307

Create detailed provider implementation guide with:

Architecture overview and implementation steps
Configuration patterns and best practices
Testing checklist and Docker integration guide
Example using Together AI implementation

Add Together AI as new provider with:

Environment variables and Docker configuration
Support for Qwen, Llama, and Mixtral models
API key and base URL management
OpenAI-compatible API integration

Question ?
I wrote a small documentation about the AI Provider Architecture and implementation steps to add new provider in the future. Where should it be stored, is there a knowledge base, wiki or storage somewhere?

AI Provider Implementation Guide
Architecture Overview
The system follows a modular architecture for managing LLM providers and their models. Here's how the components interact:

Application Layer: Orchestrates the initialization and dynamic loading of providers and models
PROVIDER_LIST: Contains static configurations and dynamic loading capabilities for each provider
ModelList: Maintains the combined list of static and dynamically loaded models
Dynamic Providers: Handles runtime model discovery and API interactions
External APIs: The actual LLM provider services

Diagram

Implementation Steps
1. Environment Variables Setup
First, add the necessary environment variables in .env.example:
# Provider API Base URL (if required)
PROVIDER_NAME_API_BASE_URL=

# Provider API Key (if required)
PROVIDER_NAME_API_KEY=

Example from Together AI implementation:
TOGETHER_API_BASE_URL=
TOGETHER_API_KEY=

2. Docker Configuration
Update the Docker-related files to include the new provider's environment variables:

Update Dockerfile:

# Add in both build and runtime stages
ARG PROVIDER_NAME_API_KEY
ARG PROVIDER_NAME_API_BASE_URL

# Add to ENV section in both stages
ENV PROVIDER_NAME_API_KEY=${PROVIDER_NAME_API_KEY} \
    PROVIDER_NAME_API_BASE_URL=${PROVIDER_NAME_API_BASE_URL}

Update docker-compose.yaml:

services:
  app:
    environment:
      - PROVIDER_NAME_API_KEY=${PROVIDER_NAME_API_KEY}
      - PROVIDER_NAME_API_BASE_URL=${PROVIDER_NAME_API_BASE_URL}

3. Type Definitions
Add the environment variable types to worker-configuration.d.ts:
interface Env {
  PROVIDER_NAME_API_KEY: string;
  PROVIDER_NAME_API_BASE_URL: string;
}

4. Provider List Configuration
Add the provider information in app/utils/constants.ts. This is the entry point for both static and dynamic model configurations:
const PROVIDER_LIST: ProviderInfo[] = [
  {
    name: 'ProviderName',
    staticModels: [
      {
        name: 'model-identifier',
        label: 'Display Name',
        provider: 'ProviderName',
        maxTokenAllowed: 8000,
      }
    ],
    getDynamicModels: async (apiKey: string, baseURL: string) => {
      // Implementation for dynamic model loading
      return [/* ModelInfo[] */];
    }
  }
];

5. API Key and Base URL Handling
Modify app/lib/.server/llm/api-key.ts to include the new provider:
// API Key Resolution
export function getAPIKey(cloudflareEnv: Env, provider: string, userApiKeys?: Record<string, string>) {
  switch (provider) {
    case 'ProviderName':
      return env.PROVIDER_NAME_API_KEY || cloudflareEnv.PROVIDER_NAME_API_KEY;
    // ... other providers
  }
}

// Base URL Resolution
export function getBaseURL(cloudflareEnv: Env, provider: string) {
  switch (provider) {
    case 'ProviderName':
      return env.PROVIDER_NAME_API_BASE_URL || cloudflareEnv.PROVIDER_NAME_API_BASE_URL;
    // ... other providers
  }
}

6. Model Implementation
Update app/lib/.server/llm/model.ts to handle the new provider:
export function getModel(provider: string, model: string, env: Env, apiKeys?: Record<string, string>) {
  const apiKey = getAPIKey(env, provider, apiKeys);
  const baseURL = getBaseURL(env, provider);

  switch (provider) {
    case 'ProviderName':
      return getProviderNameModel(baseURL, apiKey, model);
    // ... other providers
  }
}

// Provider-specific implementation
function getProviderNameModel(baseURL: string, apiKey: string, model: string) {
  return {
    generate: async (prompt: string, options: GenerateOptions) => {
      // Implementation
    },
    // Additional methods
  };
}

7. Dynamic Model Loading (Optional)
If your provider supports dynamic model discovery, implement the getDynamicModels function:
async function getProviderNameModels(apiKey: string, baseURL: string): Promise<ModelInfo[]> {
  try {
    const response = await fetch(`${baseURL}/models`, {
      headers: {
        'Authorization': `Bearer ${apiKey}`,
      },
    });

    const data = await response.json();
    return data.models.map(model => ({
      name: model.id,
      label: model.name,
      provider: 'ProviderName',
      maxTokenAllowed: model.context_length,
    }));
  } catch (error) {
    console.error('Failed to fetch models:', error);
    return [];
  }
}

Implementation Patterns
1. OpenAI-Compatible APIs
For providers offering OpenAI-compatible APIs (like Together AI):
case 'ProviderName':
  return getOpenAILikeModel(baseURL, apiKey, model);

2. Custom APIs
For providers with unique APIs:
function getProviderNameModel(baseURL: string, apiKey: string, model: string) {
  return {
    generate: async (prompt: string, options: GenerateOptions) => {
      const response = await fetch(`${baseURL}/generate`, {
        method: 'POST',
        headers: {
          'Authorization': `Bearer ${apiKey}`,
          'Content-Type': 'application/json',
        },
        body: JSON.stringify({
          model,
          prompt,
          // Provider-specific options
        }),
      });

      return handleProviderResponse(await response.json());
    },
  };
}

Example: Together AI Implementation
The Together AI implementation demonstrates using the OpenAI-compatible API pattern:

Environment Variables:

TOGETHER_API_BASE_URL=
TOGETHER_API_KEY=

Docker Configuration:

ARG TOGETHER_API_KEY
ARG TOGETHER_API_BASE_URL

ENV TOGETHER_API_KEY=${TOGETHER_API_KEY} \
    TOGETHER_API_BASE_URL=${TOGETHER_API_BASE_URL}

Provider List Configuration:

{
  name: 'Together',
  staticModels: [
    {
      name: 'meta-llama/Llama-3.2-90B-Vision-Instruct-Turbo',
      label: 'meta-llama/Llama-3.2-90B-Vision-Instruct-Turbo',
      provider: 'Together',
      maxTokenAllowed: 8000,
    }
  ],
}

API Integration:

case 'Together':
  return getOpenAILikeModel(baseURL, apiKey, model);

Testing Checklist

Environment Setup

[x] Add required environment variables
[x] Configure API keys and base URLs
[ ] Update Docker configurations

Static Configuration

[x] Verify provider list entry
[x] Confirm static model definitions

Dynamic Loading

[ ] Test dynamic model fetching
[ ] Verify error handling

API Integration

[x] Test model generation
[x] Verify response handling
[ ] Check token limits

Error Handling

[x] Test invalid API keys
[ ] Verify rate limit handling
[x] Check error messages

Docker Integration

[ ] Test building Docker image with new variables
[ ] Verify environment variable passing
[ ] Test Docker Compose configuration

Best Practices

Error Handling: Implement comprehensive error handling for API calls
Rate Limiting: Consider implementing rate limiting for API calls
Validation: Validate API responses and model configurations
Documentation: Document provider-specific features and limitations
Testing: Create tests for both success and failure scenarios
Docker: Follow the existing pattern for environment variable handling in Docker configurations

Notes

Follow existing patterns for error handling and response formatting
Consider rate limiting and quota management
Document any provider-specific limitations or requirements
Update relevant configuration types and interfaces
Ensure Docker configurations are consistent with existing providers

wrote a small documentation about the AI Provider Architecture and implementation steps to add new provider in the future. Where should it be stored, is there a knowledge base, wiki or storage somewhere?

I would say, separate md file linked from readme?

Got to test together ai and does not work unless env has https://api.together.xyz/v1 setup
But why do we need it in env? It could be hardcoded no?


Create self evaluation mode for recalling digits

Currently, the fragment which handles recall only has the option to view the recited numbers one by one or view them all at once. It would be better to include a self evaluation mode, wherein the user can type in the memorized digits one by one and upon pressing a button, would show them how many of their entries were correct.
There should be a switch in the 'main' fragment to enable or disable the self-evaluation mode. The enabled option should be saved to sharedPreferences and should display the self-evaluation fragment in the recall mode. If disabled, the older recall fragment (with the regular view digits one by one or view them together) should be used.

Implemented!


Sync installer SHA

Pick up changes to upgrade prom, fix istiod, and fix injection template

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
5eafc50bb704ec52c6b0ac4a6eec868d558cc39e
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e_operator

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
5eafc50bb704ec52c6b0ac4a6eec868d558cc39e
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

test failure is real, looking into it

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
5eafc50bb704ec52c6b0ac4a6eec868d558cc39e
link
/test e2e_operator

mandiff_operator
c365213d7c1f1d909ea362ce80052f1d03cc02da
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
c4618ac491083c9bba085792367304462d1f7f17
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e_operator
c4618ac491083c9bba085792367304462d1f7f17
link
/test e2e_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Feature Request] Add letters to distinguish between layers for color blind people

Would it be possible to (optionally) add letters to be able to distinguish between layers for color blind people? The lead EA in our team is completely color blind, so is not able at all to distinguish between the different colors of the different layers of the elements. If it were possible to add letters to the elements, like Example 34 in the spec show, that would allow us to adopt this tool within our organization.
Version 3.1:
https://pubs.opengroup.org/architecture/archimate3-doc/chap12.html#_Toc437870133

Version 3.2:
https://pubs.opengroup.org/architecture/archimate32-doc/#_Toc437870133

If you use Label Expressions you can add anything you like.

I'm not sure if I follow. If I were able to set default label expressions per element type, this would implement my request. However, it seems that I can only set this per element. I'd have to do this for every element individually. Is this correct or is there an option to configure label expressions model-wide?

I'm not sure if I follow. If I were able to set default label expressions per element type, this would implement my request. However, it seems that I can only set this per element. I'd have to do this for every element individually. Is this correct or is there an option to configure label expressions model-wide?

That's correct. You don't have to user letters. You could use a different signifier.

Hi,
My 2 cents on this (also apply to PR #908)...

A good architecture diagram should not need such thing to distinguish between layers as there should be no ambiguity in 90% of the cases (the viewpoint used, the view title and the legend should be enough). I would even argue that if there is ambiguity, then this is an issue with the view itself, not the person who tries to understand it.
In 90% of the remaining 10%, you can most of the time magically solve the issue by nesting the behavior inside its active structure, which is unambiguous.
For views that mix elements from multiple layers and for which such hint is needed (thus the remaining 1% from previous points), then a label expression should do the trick (see issue #870 for some examples). Setting a label expression on all elements from a view is as simple as: select all elements, then edit the label once and for all. Should you know people who can't remember the label to put, then a simple script can also do it.

So as you might have already understood, I don't see such change as a priority in Archi.

You could also use a simple grouping mechanism to add the viewed elements in the group of its layer.

I'll close this one given above feedback.


Not working when use loadImageFromFile

Editor buttons not working when init image with loadImageFromFile.
Check this: https://stackblitz.com/edit/js-qovzzf?file=index.js

@bilalmalkoc
Thank you for the information.
On the link you gave me, loadImageFromFile is working well.
Can you explain it in detail?

Did you try edit image? @lja1018

@bilalmalkoc
Nothing is working. I'll find it and fix it.

@yc-codes
I'm sorry, but it hasn't been updated yet.

not working for me, i have a hard coded base64 string and converting it to file object, nothing happens, will try using input type file, let's see


⚠ Bofrost.be has degraded performance

In 1cb5ffa, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 3017 ms

Resolved: Bofrost.be performance has improved in 68e5358.


Add to Swift Package Index

https://swiftpackageindex.com/add-a-package

Already done! Thanks to Sven.
https://github.com/SwiftPackageIndex/PackageList/issues/6728


  You can already do this with sites like jsfiddle, where I can author some content, save it, get a URL and when you open it, you get back the same content.  I want to be able to do this with an entire web project that has many files.  In essence, you're opening not only an editor, but also a project via a single URL.
Solving this completely likely requires server-side code, but there will be aspects of this that are Brackets facing.  Specifically, we currently assume that we'll get content for a single HML file from the parent window via postMessage, and then save this to /index.html.  It would be nice to figure out a way to allow more complex hierarchies to be used.  Maybe we should use something like tar in JS to allow passing a single stream which we can then expand into the filesystem.
@modeswitch, did you implement tar/untar at some point for filer?  Can you point me at what you did, if so?

Talked to @modeswitch on irc, and his old tar code is in this commit: https://github.com/filerjs/filer/commit/ad3aa5eac8f7730009ad7c1fe84cccfb133a7c7c

It would be interesting to think about publishing as "tar the filesystem, and send that to the server" and edit/open as "xhr a tar file from the server and expand to the filesystem."

Yeah, that's a wonderful idea.
I had planned to add support for something like this as an option during formatting anyway, and this would be a more general version of that.

@humphd Have we already solved this? If not, we'll need to. I suspect your patch to switch makedrive providers might do the trick.

We're solving this in Thimble, closing here.

FYI, I'm doing this in Bramble and Thimble (starting with Bramble here https://github.com/humphd/brackets/pull/416).  I ended up using https://github.com/humphd/bitjs, which I forked from Google Code.  It's really great, because it does it on a worker.


Microsoft.AspNetCore.Identity.UI.csproj failed to load

git clone code, then load it in VS 2017 ver 15.7.1
Microsoft.AspNetCore.Identity.UI.csproj load failed.

@javiercn ?

Did you try running the build.cmd file first, rather than using VS?

Yes. Also %userprofile%/.dotnet/x64 needs to be on the path when you launch Visual Studio for it to pick up the right dotnet to use.

Thanks guys. I missed that path. After I add it and run build.cmd, I can compile the code without errors.
Is there a document can walk me through how to use it? Which project should I use to generate database? I am new to .Net core. Thanks for the help.

I have set default project to 'sample\IdentitySample.DefualtUI in Package Manager Console, and run 'update-database'.
I got an error 'The EntityFramework package is not installed on project 'Identity.DefaultUI.WebSite'.'
I checked its dependency which has 'Microsoft.EntityFrameworkCore.Tools;.
Why I cannot run 'Update-Database'?

Can you run add migration and then update database? Also try from the command-line “dotnet ef database update” on the project folder.

D:_GIT\Identity\samples\IdentitySample.DefaultUI>dotnet ef database update
No executable found matching command "dotnet-ef"
PM> Add-Migration ddd
The EntityFramework package is not installed on project 'IdentitySample.DefaultUI'.
I am really confused. Normally, I do update-database in EF6.

This is my dotnet, not sure if I have the right version

is that after running build.cmd?
You should do dotnet --info which will give you the exact information.

why can't I use ' dotnet ef database update'?

You are on an older version of dotnet. You need to run build.cmd and use the version on %userprofile%/.dotnet/x64

thanks for the help @javiercn
I found the following url. It helped, just like you said I should replace the default .net core with whatever in %userprofile%/.dotnet/x64.  I can start the sample now.
https://github.com/aspnet/Home/wiki/Building-from-source#path

Closing this as there's no further action required.


Added additional APIs to better support JNI on Spark

Performance improvement for prediction is roughly 3-4x on our datasets.
Training data loading was also improved by avoiding memory copy. Performance measurements are still in progress.

@StrikerRUS I think we can use these apis to improve the prediction in python package as well


no character creating?

i once was able to make a character on my test server, it logs in fast, but when i get to the create character it says max already made, yet none show.. wont go any further

Nothing to do with ZD in particular, you should check out the forums for settings related to max characters per account etc.


Setup issue

facing issue to set up the repo when try run this project then show that
pnpm dev

<EMAIL_ADDRESS>devv
next dev

node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
Error: Cannot find package ' \repo\retroui\node_modules.pnpm@effect-ts+otel-exporter-trace-otlp-grpc@0.15.1_@effect-ts+core@0.60.5_@opentelemetry+api<EMAIL_ADDRESS>imported from \repo\retroui\node_modules.pnpm@effect-ts+otel-exporter-trace-otlp-grpc@0.15.1_@effect-ts+core@0.60.5_@opentelemetry+api<EMAIL_ADDRESS>Did you mean to import @opentelemetry+exporter-trace-otlp-grpc@0.39.1_@opentelemetry+api<EMAIL_ADDRESS>at legacyMainResolve (node:internal/modules/esm/resolve:214:26)
at packageResolve (node:internal/modules/esm/resolve:840:14)
at moduleResolve (node:internal/modules/esm/resolve:910:20)
at defaultResolve (node:internal/modules/esm/resolve:1130:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
at ModuleWrap. (node:internal/modules/esm/module_job:85:39)
at link (node:internal/modules/esm/module_job:84:36) {
code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v20.11.0
 ELIFECYCLE  Command failed with exit code 1.

 although I installed using pnpm

 pnpm i
Lockfile is up to date, resolution step is skipped
Packages: +662
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 662, reused 662, downloaded 0, added 662, done
<EMAIL_ADDRESS>Running postinstall script, done in 887ms
node_modules/.pnpm/contentlayer<EMAIL_ADDRESS>Running postinstall script, done in 1.4s
dependencies:

@headlessui/react 2.1.9
@radix-ui/react-avatar 1.1.1
class-variance-authority 0.7.0
clsx 2.1.1
contentlayer 0.3.4
date-fns 4.1.0
lucide-react 0.445.0
next 14.2.7
next-contentlayer 0.3.4
react 18.0.0
react-dom 18.0.0
rehype-pretty-code 0.14.0
rehype-slug 6.0.0
tailwind-merge 2.5.3
unist-builder 4.0.0
unist-util-visit 5.0.0

devDependencies:

@types/node 20.0.0
@types/react 18.0.0
@types/react-dom 18.0.0
eslint 8.0.0
eslint-config-next 14.2.7
postcss 8.0.0
tailwindcss 3.4.1
typescript 5.0.2

Done in 24.6s

  can you please help issue facing

unfortunately I couldn't recreate your scenario.. I cloned the project in a new folder but it was working fine for me.
Can you delete the project and create a new? if that doesn't solve it, please shoot me a DM on discord and we can get in a call to resolve this.

I tried three times. Maybe I will ask in discord thanks for your time.


Support PEP 625 (Filename of a Source Distribution)

What's the problem this feature will solve?
PEP 625 has been accepted, PyPI should be updated to support the PEP.
Describe the solution you'd like
PyPI needs to implement some changes to support the PEP:

a restriction on the filenames considered valid for a source distribution (and a corresponding deprecation/notification)
validation of the distribution and version sections of the filename, including normalization.

This is likely blocked on https://github.com/pypa/packaging/issues/527.

This is probably also blocked on finding a good migration path that isn't too obtrusive for users. Right now, there are a lot of files being uploaded that would fail to upload once this change is implemented, and IMO this would break too many users for us to enable this right now:
warehouse=> select DATE_TRUNC('day', upload_time) as day, count(filename) from release_files where packagetype = 'sdist' and filename ilike '%-%-%' group by DATE_TRUNC('day', upload_time) order by day desc limit 30;
         day         | count
---------------------+-------
 2023-06-26 00:00:00 |  1028
 2023-06-25 00:00:00 |   381
 2023-06-24 00:00:00 |   687
 2023-06-23 00:00:00 |  1093
 2023-06-22 00:00:00 |  1453
 2023-06-21 00:00:00 |  1486
 2023-06-20 00:00:00 |  1606
 2023-06-19 00:00:00 |  1200
 2023-06-18 00:00:00 |   354
 2023-06-17 00:00:00 |   723
 2023-06-16 00:00:00 |  1455
 2023-06-15 00:00:00 |  1161
 2023-06-14 00:00:00 |  1567
 2023-06-13 00:00:00 |  1557
 2023-06-12 00:00:00 |  1157
 2023-06-11 00:00:00 |   358
 2023-06-10 00:00:00 |   693
 2023-06-09 00:00:00 |  1327
 2023-06-08 00:00:00 |  1958
 2023-06-07 00:00:00 |  1631
 2023-06-06 00:00:00 |  1430
 2023-06-05 00:00:00 |  1116
 2023-06-04 00:00:00 |   325
 2023-06-03 00:00:00 |   783
 2023-06-02 00:00:00 |  1327
 2023-06-01 00:00:00 |  1710
 2023-05-31 00:00:00 |  1693
 2023-05-30 00:00:00 |  1109
 2023-05-29 00:00:00 |   959
 2023-05-28 00:00:00 |   387
(30 rows)

I think a good migration path would be:

ensuring the most popular build tools have supported outputting PEP 625-compliant filenames for some sufficiently long period of time
perhaps making upload tools like twine silently normalize this at upload time, possibly with a warning?

The other thing we could do, is forcibly normalize ourselves, though we hadn't done that in the past and I know that would break at least twine's checks if a file has been uploaded already.

Blocked on #14156 as well.

Until the version in the sdist filename is verified as described in this issue, it's possible to create multiple sdists per release (as seen from the filename point of view).
Example: upload foo-1.tar.gz with release 1 and foo-1.zip with release 1.1. From the metadata point of view it's still just one sdist per release, but from the Simple API point of view (which the package managers use) there are two sdists for release 1.
This does not seem to be in the spirit of PEP 527:

[T]his PEP proposes to allow one, and only one, sdist per release of a project.

Which is currently verified on upload.

Probably also blocked on https://github.com/pypa/setuptools/issues/3593 as the predominant builder of source distributions.

There doesn't seem to be any real progress here towards builders producing normalized source distribution filenames:
warehouse=> SELECT DATE_TRUNC('month', upload_time) AS month, COUNT(filename)
FROM release_files
WHERE packagetype = 'sdist'
    AND filename ILIKE '%-%-%'
    AND upload_time >= DATE_TRUNC('month', CURRENT_DATE) - INTERVAL '30 months'
GROUP BY DATE_TRUNC('month', upload_time)
ORDER BY month DESC;
        month        | count
---------------------+-------
 2024-03-01 00:00:00 | 23683
 2024-02-01 00:00:00 | 31742
 2024-01-01 00:00:00 | 33589
 2023-12-01 00:00:00 | 33818
 2023-11-01 00:00:00 | 35584
 2023-10-01 00:00:00 | 32092
 2023-09-01 00:00:00 | 33117
 2023-08-01 00:00:00 | 38100
 2023-07-01 00:00:00 | 34178
 2023-06-01 00:00:00 | 35241
 2023-05-01 00:00:00 | 35136
 2023-04-01 00:00:00 | 32816
 2023-03-01 00:00:00 | 39726
 2023-02-01 00:00:00 | 34714
 2023-01-01 00:00:00 | 32340
 2022-12-01 00:00:00 | 26588
 2022-11-01 00:00:00 | 29160
 2022-10-01 00:00:00 | 27748
 2022-09-01 00:00:00 | 30693
 2022-08-01 00:00:00 | 35739
 2022-07-01 00:00:00 | 30297
 2022-06-01 00:00:00 | 31412
 2022-05-01 00:00:00 | 35092
 2022-04-01 00:00:00 | 29901
 2022-03-01 00:00:00 | 33199
 2022-02-01 00:00:00 | 27257
 2022-01-01 00:00:00 | 28129
 2021-12-01 00:00:00 | 27028
 2021-11-01 00:00:00 | 30112
 2021-10-01 00:00:00 | 30402
 2021-09-01 00:00:00 | 28612
(31 rows)

https://github.com/pypa/setuptools/issues/3593 has been closed (implemented) for a little while now, would be interesting to see if it is yet making a dent in that graph

Indeed, quite a nice drop:

At this rate, we should be low enough in another month or two to start emitting warnings about a deprecation, and probably by EOY we could fully support PEP 625.

And here's the latest:

Less than 10K uploads in October.

PR to start warning uploaders of non-PEP 625 compliant filenames is here: #17110

Hi,
This change is creating some confusion in the Django project (unsurprisingly, considering the non-standard capitalization of our package and build files historically), especially around the timeline and extent of the deprecation: https://code.djangoproject.com/ticket/35980.
Our current solution has been to pin setuptools but that's not a solution we're keen to keep in the long term.
Could you clarify what you meant in the comment above with "[...] probably by EOY we could fully support PEP 625."? Does that mean that non-pep625 build files could start being rejected, or is that just a prediction about the progress towards the goal of all newly uploaded build files being pep625-compliant?
The warning email from PyPI that Django received with our latest release also mentions that "In the future, PyPI will require all newly uploaded source distribution filenames to comply with PEP 625.". Is there a clearer timeline for this? Will there be a mechanism where maintainers will be given advance notice of that change, or is there a specific GH issue one could subscribe to for example?
Django has a major version set to be released in April, and it would be helpful for our maintainers to know whether we need to audit/fix our various release scripts and documentation ahead of that date.
Thanks for all the work you do on PyPI, we're big fans 🎉

Hi @bmispelon, thanks for your comment here, sorry this is causing confusion for the Django project.

Could you clarify what you meant in the https://github.com/pypi/warehouse/issues/12245#issuecomment-2272378958 with "[...] probably by EOY we could fully support PEP 625."? Does that mean that non-pep625 build files could start being rejected, or is that just a prediction about the progress towards the goal of all newly uploaded build files being pep625-compliant?

By "fully support PEP 625" I meant that PyPI would be in compliance with PEP 625, and reject uploads of filenames that are invalid per PEP 625. I think it's unlikely that we actually will do this by EOY, though.

Is there a clearer timeline for this? Will there be a mechanism where maintainers will be given advance notice of that change, or is there a specific GH issue one could subscribe to for example?

We don't currently have a timeline other than "eventually". If it's helpful, I can commit to having the warning emails include a clear deadline at a minimum of 6 months before said deadline, and share that deadline on this issue as well. Would that suffice? That also means this wouldn't be enforced before Django's release in April.
FWIW, I think this change should be unnecessary -- the actual project name shouldn't need to change, just the underlying build tooling that is producing the source distribution. In this case, upgrading setuptools should be all that is necessary (aside from project-specific changes to handle the new filename, of course).

To add more context to this, the project name is used in different places with different normalizations: There is the human-readable name, and there is the dist-info name (re.sub(r"[-_.]+", "_", name).lower()). Note that the dist-info normalization is different from the regular package name normalization (re.sub(r"[-_.]+", "-", name).lower()) to avoid a dash in a name that is delimited by a dash.

pyproject.toml project.name: human-readable name ("Tools SHOULD normalize this name, as soon as it is read for internal consistency.")
METADATA Name: Same as pyproject.toml project.name
Source distribution filenames: dist-info name
Wheel filename: dist-info name
The top level <name>-<version> directory inside a source distribution: dist-info name. This isn't explicitly called out in the spec, but it uses {name}-{version} for both filename and top level directory. It doesn't impact tooling as there is only one top level directory anyway.
<name>-<version>.dist-info and <name>-<version>.data directories inside the wheel: dist-info name.  This isn't explicitly called out in the spec, but it uses {distribution}-{version} for both filename and .dist-info names and unnormalized names would cause ambiguity after installation.

I do not think that even https://github.com/pypa/setuptools/issues/3777 is a blocker here, though it might take a slightly pedantic reading to agree with this.
As I understand it, this issue is specifically about PEP 625 and source distribution names: so though it seems to be true that setuptools is producing wheels whose naming is not PEP-491 compliant - that would be out of scope.
There probably should be an analogous issue here for wheels: "support [enforce] PEP491".  But I think that is not what this issue says, and I guess it is unlikely that warehouse would insist on PEP-491 while setuptools produces non-compliant wheels.

I do not think that even pypa/setuptools#3777 is a blocker here, though it might take a slightly pedantic reading to agree with this.
As I understand it, this issue is specifically about PEP 625 and source distribution names: so though it seems to be true that setuptools is producing wheels whose naming is not PEP-491 compliant - that would be out of scope.
There probably should be an analogous issue here for wheels: "support [enforce] PEP491". But I think that is not what this issue says, and I guess it is unlikely that warehouse would insist on PEP-491 while setuptools produces non-compliant wheels.

Hi! This is Natalia, one of the current Django Fellows. Thank you David for your feedback!
For Django, the release process uses a unified workflow that relies on setuptools to generate both the tarball and the wheel. However, the issue with setuptools is that it produces a lowercase django tarball and a capitalized Django wheel. This inconsistency complicates our tooling, which must handle both naming formats. Ideally, we would have a consistent naming convention across both formats to avoid this problem.
As a workaround, we’ve been pinning setuptools>=61.0.0,<69.3.0 to produce consistently named Django tarballs and wheels. However, this triggers the current deprecation warning when uploading to PyPI, and for Django, the inconsistent wheel naming is a blocker to releasing tarballs with the expected naming format.

Ah, then I guess https://github.com/pypa/setuptools/issues/3777 is a blocker specifically for django - but still not, strictly speaking, a blocker here...
setuptools sounds open to pull requests fixing this and I assume that it must be not very difficult once the relevant bit of code is identified, perhaps you are motivated to make that happen.

Ah, then I guess pypa/setuptools#3777 is a blocker specifically for django - but still not, strictly speaking, a blocker here...

Ish :-)
I believe this inconsistency (which goes beyond just name casing) could affect more packages than just Django, for similar reasons. It’s problematic and likely complicates tooling to have release artifacts with varying casing or punctuation.

setuptools sounds open to pull requests fixing this and I assume that it must be not very difficult once the relevant bit of code is identified, perhaps you are motivated to make that happen.

👍


feat: Automated rollback of failed release

Once a helm release is failed, further effective helm upgrade --install runs can be prevented forever.
To work-around the issue, on every install/upgrade failure, helmfile should automatically run either helm delete --purge or helm rollback against the failed release according to the current revision number(1 or greater).
Relevant upstream issues are:

https://github.com/helm/helm/pull/3097#issuecomment-417178786
https://github.com/helm/helm/issues/3353#issuecomment-385222233

We’ve been using the —force helm arg to mitigate this. It will upgrade a failed release.

@osterman Thanks! Makes sense.
Then only thing remaining unclear to me is how upgrade --install --force works when it failed on first run.
According to @whereisaaron's comment at https://github.com/helm/helm/issues/3353#issuecomment-385222233, we seem to need helm delete --purge in that case, instead of rolling back. If upgrade --install --force works well in both cases, I can be a superior solution!

It's unclear to me whether --force is ever destructive.
An example of undesirable behavior would be if the --force flag ever causes a Deployment in a failed release to be deleted before it's "re-upgraded".

You need the --purge because you can't (couldn't) upgrade a release that has never been successfully deployed. Even if you helm delete it. If you still can't upgrade a release that fails on its first attempt, then --purge is the only available way to handle that state I think?

@whereisaaron, there is a --force flag available on newer versions of helm upgrade that seems to auto-purge under certain conditions.

https://github.com/roboll/helmfile/pull/491 should fix this also

Is this in now?  As I've just been burned by it:
UPGRADE FAILED
ROLLING BACK
Error: no CustomResourceDefinition with the name "meshpolicies.authentication.istio.io" found
Error: UPGRADE FAILED: no CustomResourceDefinition with the name "meshpolicies.authentication.istio.io" found

Could you try adding --atomic? The behaviour is currently opt-in. But if
you like I'd be eager to make it on by default!
2019年3月21日(木) 5:26 Karl Stoney<EMAIL_ADDRESS>
Is this in now? As I've just been burned by it:
UPGRADE FAILED
ROLLING BACK
Error: no CustomResourceDefinition with the name "meshpolicies.authentication.istio.io" found
Error: UPGRADE FAILED: no CustomResourceDefinition with the name "meshpolicies.authentication.istio.io" found
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/roboll/helmfile/issues/256#issuecomment-475014141,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABV-QwalqK5F5ZyO_lZjZS4v529JxNlks5vYplqgaJpZM4WSuAd
.

@Stono Does setting atomic: true for your releases solves your issue? I'm going to make it default to true in the future #512

@mumoshu hey - i haven't had chance to check but i don't think you should change the default behaviour of helmfile to be different to that of helm.
For context as you know we have 200+ applications deployed and our ci/cd tooling manages rollbacks automatically for us, we wouldn't want helmfile taking that responsibility and we would also rather not go and edit 200+ helmfiles to deal with this API change!

If you are going to change the default behaviour, would it be possible to provide a flag to opt out of this behaviour instead of having to specify it in a helmfile.yaml? i.e. helmfile sync --no-atomic

@Stono @mikespokefire Thanks for the feedbacks!
I'm happy with just adding the --atomic to helmfile and keeping the default behavior as-is.
Would it work for you both?

That would be much preferred.
I think a general rule of not deviating from default helm behaviour where
possible will make helmfile adoption simpler!easierSwipe
On Thu, 30 May 2019, 07:22 KUOKA Yusuke<EMAIL_ADDRESS>wrote:

@Stono https://github.com/Stono @mikespokefire
https://github.com/mikespokefire Thanks for the feedbacks!
I'm happy with just adding the --atomic to helmfile and keeping the
default behavior as-is.
Would it work for you both?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/roboll/helmfile/issues/256?email_source=notifications&email_token=AALK7CNMBF5TDZOCVGX24H3PX5XB3A5CNFSM4FSK4AO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWRPKOY#issuecomment-497218875,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALK7CKVGO2AP6VO24PF3W3PX5XB3ANCNFSM4FSK4AOQ
.

Noted. Thanks for your confirmation and the support ☺


Recipe app

Link to project
[ ] Number of members: 2

@martinkarugaba
@mryeminthu

Hi Team,
Good job so far, indeed you have spent time on this project!
There are some issues that you still need to work on to go to the next project but you are almost there!
Highlights

Good use of Kanban board ✔

Required Changes ♻
Check the comments under the review.

[ ] I can see you have your description except the last one which I encourage you to add but the number of points is yet to be added, the point should serve as the expected number of time the student should work on it, kindly add it for each task.

[ ] I noticed that some tasks are not shown at all in your project division such as recipe list, I will encourage you to use the pointed ones in the image below as the descriptive heading of each card and use the tasks under them as the detailed description so that it would entail all tasks.

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Hi @martinkarugaba 👋🏼👋🏼👋🏼,

Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights✅✅✅

[x] The required cards have been added as requested by the previous reviewer👍🏼.

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


[Win] Test installation with TAP-Windows 2.21.2

https://github.com/subutai-io/tray/issues/103
Need to test installation with updated drivers on Win10, win 7 and win 8

Tested


Has AppCenter SDK output changed?

I'm having problems with App Center log output showing up in App Center, but I can see all the events, crashes, and handled exceptions I'm generating in my app output to the Debug Consoles as well as Android logCat.  I never see the message "App Center SDK configured successfully," but I do see "App Center initialized."
The log output also shows logs successfully sent to App Center, as indicated by the HTTP 200 response that's logged immediately after the view of the JSON object that's sent.  If the SDK wasn't configured correctly, would it still log correctly and POST the logs to App Center?  If it is configured correctly but the sample output isn't shown, does that mean this documentation needs to be updated?

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

ID: af635c53-8b58-a6c4-bd0f-cefb71bbfee4
Version Independent ID: c388dd37-6b0c-47f0-b2a1-58590b3d3de5
Content: Xamarin SDK Troubleshooting - Visual Studio App Center
Content Source: docs/sdk/troubleshooting/xamarin.md
Service: vs-appcenter-sdk
Sub-service: app-center-general
GitHub Login: @elamalani
Microsoft Alias: emalani

Hey @MrXemiu! No, we haven't changed anything related to that. Please tell me when have you stopped seeing this message (with what SDK version)? Could you include the sample of such logs?
Thanks.

Thanks for filing this report & sorry that you haven't heard back from us. It sounds like this issue for technical support, but this repository isn't monitored by our support team.
If you need technical help, you can contact support by:

Going to https://appcenter.ms/apps
Selecting ? > Contact Support (in the upper right corner).
Reference this issue for context if needed.

If you've already resolved your issue/still want us to document this, give us an update of your current observations. We're catching up on our backlog here.

I'll review logcat output tomorrow and verify whether I see "App Center SDK configured successfully," and let you guys know.


Add a benchmark suite

It would be useful to see how the performance changes between each release

Closing, as  0a8678286fad930fb8ac880cd1661b384b789f2a adds a note regarding this. This may however be added later, but not prioritized for now, as it makes more sense to benchmark helm and kubernetes instead. Thus, it should perhaps be part of the deployment script instead.


[SPARK-15363][ML][Example]:Example code shouldn't use VectorImplicits._, asML/fromML

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
In this DataFrame example, we use VectorImplicits._, which is private API.
Since Vectors object has public API, we use Vectors.fromML instead of implicts.
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
Manually run the example.

Test build #58941 has started for PR 13213 at commit 818dc7f.

Test build #58941 has finished for PR 13213 at commit 818dc7f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58941/
Test PASSed.

LGTM. Merged into master and branch-2.0. Thanks!


[Docs] Corrected default value of mesheryctl mesh deploy --adapter

Description
[Docs] The default value of mesheryctl mesh deploy --adapter is inconsistent
This PR fixes #
#867
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit 27705bfda3aa2468767c9124ca970c6a4127b6ff at: https://636cf33cfce5d914e19fbfe4--meshery-docs-preview.netlify.app

@RahulSurwade08 Thanks for your contribution! I looked again and found another mistake here: https://docs.meshery.io/reference/mesheryctl/mesh/validate

Can you fix it too?

@rahulsurwade did you mean to close this PR?


ERC20.lua:89: attempt to concatenate field 'symbol' (a nil value)

Hi,
I am getting this error message for a couple of weeks now everytime I try to add a new ETH address to MoneyMoney or when I try to update existing accounts:
ERC20.lua:89: attempt to concatenate field 'symbol' (a nil value)

Hi,
Thanks for the report! I can’t reproduce the issue here, but I think https://github.com/aaronk6/ERC20-MoneyMoney/commit/17829b59b20fe5830896937d81a5b2bb82a3349f will fix it. I’ve submitted a new version to MoneyMoney. So a signed version for you to try will be available soon.

@cryptochrome Would you mind trying the latest release (https://github.com/aaronk6/ERC20-MoneyMoney/releases/tag/v1.05) and let me know if this fixes the error message?

@cryptochrome Would you mind trying the latest release (https://github.com/aaronk6/ERC20-MoneyMoney/releases/tag/v1.05) and let me know if this fixes the error message?

Just tried it, works like a champ. No more error messages :)  Thanks for fixing it!


NameError for missing os import in graphein.protein.graphs

When using the construct_graph function in a jupyter notebook, I encountered this error:
File ~/env/python3.10/site-packages/graphein/protein/graphs.py:764, in construct_graph(config, name, pdb_path, uniprot_id, pdb_code, df, chain_selection, model_index, df_processing_funcs, edge_construction_funcs, edge_annotation_funcs, node_annotation_funcs, graph_annotation_funcs, verbose)
    761 if pdb_path is not None and isinstance(pdb_path, Path):
    762     pdb_path = os.fsdecode(pdb_path)
...
--> 764 # If no config is provided, use default
    765 if config is None:
    766     config = ProteinGraphConfig()

NameError: name 'os' is not defined

In the graphs.py file, there is no import os.  Adding this fixes the error.  Not sure what's going on as I've never encountered this before?

Thanks for the bug report. No idea how this slipped through testing. I'll make a new release ASAP.

Should be resolved in 1.7.0 (pip install graphein==1.7.0)


Publish as jekyll theme

I hope that your work can be installed automatically with adding gem, as described here. If you feel it necessary maybe this can be your reminder, but feel free to close it if you think it's not necessary. Thanks i love your theme :smile:

Thanks for the idea but its not going to be happening soon from my side. I will be releasing v2 for this theme with this support, since I had this approach from very begining. I am all ears for any suggestions.
Thanks for loving the theme.


Add comment author to task comment email

In the notification for new comments, we do not send out the comment's author today.
Looks like this can be done in the task mailer:
from task_mailer.rb
 def task_comment(task, comment, user)
    build_message(user.language, user.email) do
      merge_vars(user, task).merge({
        "TASK_COMMENT"    => comment.body,
        "TASK_REVIEW_URL" => handle_token_url(user.login_token.code, redirect: circle_task_path(task.circle, task)),
      })
    end
  end

@kristysnet This should hopefully be a nit to include another variable in the merge_vars to get the author of the comment. If you can add this quickly, I can then modify the template to pick up the author.

Updated templates and tested. Closing.
Thanks!

@kristysnet @phil-monroe Just realized by pushing the latest template to Mandrill, it will also be used in PROD but we will not feed the variables there yet. So for now the variable will be unfilled and look ugly but work. We should target a date for the next PROD push to rectify this (and introduce proper versioning in the not so distant future).


Access db object

Hi, i would like to access the mongodb oject used by waterline, in order to use some native mongo function. (like stats, or dump)
Does anyone know how can i achieve that.
Thanks

look this maybe be useful
http://stackoverflow.com/questions/25699097/native-update-in-sails-with-mongo-does-not-work-with-objectid

Just accessing the collection for use for base Mongo functions you can use Model.native. So say I have a model called User:
User.native(function (err, collection) {
    // Use 'collection' however you wish, e.g. collection.distinct, collection.findOne
});

Is that what you mean?

I would like to use the mongodump cli function on the global database.
I think i ll use a module like this one https://github.com/punkave/mongo-dump-stream but i still have a problem to send result to client. I posted an issue https://github.com/punkave/mongo-dump-stream/issues/4 but none answered

Hi @Oldwo1f, just a reminder:  this forum is for reporting bugs in the Sails core.  If you need support, please post to our Google Group or Stackoverflow, or try our live Gitter chat room.


Support more than one channel when masking background

The original code could only work with one channel input for masking the background. This commit adds support for more than one channel.
Checklist before merging

[x] I added an appropriate entry to CHANGELOG.md

Closes #640

This is the error we got without the fix:
2024-01-16 14:49:41,035; INFO; Now processing ROI 1/3
2024-01-16 14:49:41,118; INFO; [_preprocess_input] image_array.shape=(2, 18, 296, 316)
2024-01-16 14:49:41,118; INFO; [_preprocess_input] region=(slice(0, 18, None), slice(36, 332, None), slice(140, 456, None))
2024-01-16 14:49:41,131; INFO; [_preprocess_input] ROI_table_path='/path/230828CS001AAA48h.zarr/B/02/0/tables/organoid_ROI_table'
2024-01-16 14:49:41,131; INFO; [_preprocess_input] attrs.asdict()={'encoding-type': 'anndata', 'encoding-version': '0.1.0', 'instance_key': 'label', 'region': {'path': '../labels/organoids'}, 'type': 'ngff:region_table'}
/code/fractal-tasks-core/fractal_tasks_core/tables/v1.py:41: FutureWarning: Table type `ngff:region_table` is currently accepted instead of `masking_roi_table`, but it will be deprecated in the future. Please switch to `type='masking_roi_table'`.
  warnings.warn(warning_msg, FutureWarning)
2024-01-16 14:49:41,132; INFO; masking_label_path='/path/230828CS001AAA48h.zarr/B/02/0/tables/../labels/organoids/0'
2024-01-16 14:49:41,133; INFO; [_preprocess_input] masking_label_path='/path/230828CS001AAA48h.zarr/B/02/0/tables/../labels/organoids/0', masking_label_array.shape=(18, 540, 640)
2024-01-16 14:49:41,134; INFO; [_preprocess_input] current_label_path='/path/230828CS001AAA48h.zarr/B/02/0/labels/Organoids_test/0', current_label_array.shape=(18, 2160, 2560)
2024-01-16 14:49:41,146; INFO; Upscaling of masking label is needed
2024-01-16 14:49:41,163; INFO; background_4D.shape=(1, 18, 296, 316)
Traceback (most recent call last):
  File "/code/cellpose_2D3D_merging/src/cellpose_2d3d_merging/cellpose_2D3D_merging.py", line 918, in <module>
    run_fractal_task(
  File "/code/fractal-tasks-core/fractal_tasks_core/tasks/_utils.py", line 79, in run_fractal_task
    metadata_update = task_function(**pars)
  File "pydantic/decorator.py", line 40, in pydantic.decorator.validate_arguments.validate.wrapper_function
  File "pydantic/decorator.py", line 134, in pydantic.decorator.ValidatedFunction.call
  File "pydantic/decorator.py", line 206, in pydantic.decorator.ValidatedFunction.execute
  File "/code/cellpose_2D3D_merging/src/cellpose_2d3d_merging/cellpose_2D3D_merging.py", line 806, in cellpose_segmentation
    new_label_img = masked_loading_wrapper(
  File "/code/fractal-tasks-core/fractal_tasks_core/masked_loading.py", line 238, in masked_loading_wrapper
    ) = _preprocess_input(image_array, **preprocessing_kwargs)
  File "/code/fractal-tasks-core/fractal_tasks_core/masked_loading.py", line 175, in _preprocess_input
    image_array[background_4D] = 0
IndexError: boolean index did not match indexed array along dimension 0; dimension is 2 but corresponding boolean dimension is 1

Thanks a lot for reporting this and providing a fix for it!
@tcompa Can we reproduce this in our current test cases with a dual channel image and include a (currently failing) test that then gets solved by this PR?

Can we reproduce this in our current test cases with a dual channel image and include a (currently failing) test that then gets solved by this PR?

Done.

Thanks a lot @FranziskaMoos-FMI!


mod: use official 0.30.0 k8s deps

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
f032aa094b586f186f9e5c99305904d6a5e9d438
link
unknown
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Streaming to RTMP servers

Current behaviour
Currently KAP stores the recorded file. It would be nice to be able to store and stream the recorded interface to a rtmp server (twitch, youtube, facebook, etc). Currently the most obvious choice for most streamers on macs, would be OBS. For non tech savvy streamers, however, there is difficulty in getting this stood up creating a barrier of entry for some would-be streamers.
Suggestion
Since KAP already saves as h264 and other valid file formats, could just pass this into a binary like ffmpeg-static + ffmpeg-fluent to then broadcast the recording while downloading simultaneously, or be able to choose.
This is similar in nature to another side project i had started about 6 months ago, using webrtc to ffmpeg to stream the desktop in as few steps as possible.
I thought it would be worth having a discussion about.

It would be nice to be able to store and stream the recorded interface to a rtmp server (twitch, youtube, facebook, etc)

I imagine these streaming services require more than just an RTMP address? Probably a authentication token of some sort? I'm asking, because I'm trying to imagine how it will work with different services. I guess we'll need to implement a plugin API for streaming, so people can make plugins for their favorite service. How do you imagine this will work?

Since KAP already saves as h264 and other valid file formats, could just pass this into a binary like ffmpeg-static + ffmpeg-fluent to then broadcast the recording while downloading simultaneously, or be able to choose.

So ffmpeg is able to stream an incomplete H264 video file?

I imagine these streaming services require more than just an RTMP address? Probably a authentication token of some sort?
The services typically require a stream key and a rtmp server address. For example, twitch requires a stream key only, that is particular to your channel.

So ffmpeg is able to stream an incomplete H264 video file?
ffmpeg can do that, but i don't know if that's adviseable. If ffmpeg hits the end of a video file, it automatically concludes streaming, so if the file is still in process and is buffering, ffmpeg can prematurely stop. However, in this instance i would imagine ffmpeg would be more of a secondary path for the data buffer to flow through, ideally. I haven't dug into the aperture library, but if there's a way to give some method a callback for streaming and have it pass a buffer into something, that would be legit.

aperture.createBufferStream(ffmpegProcess)
Something like that would take advantage of the aperture performance benefits and ffmpeg wouldn't need to encode anything outside of what's required by the RTMP server.
The same process could be taken advantage of so as to use a socket relay and read the data to a canvas anywhere on the web.

So here is a small code example, if you pass a media buffer into this and fill out the necessary variables, it should stream the media to your twitch.
There's some caveats about file type. This was passing media through the mediaRecorder chrome api as h264, and using toBuffer to turn the media recorder blobs into a buffer.
Some of this is borrowed from another ffmpeg developer, (the events and logs).
var fs = require('fs');
var ffmpeg = require('fluent-ffmpeg');
var ffmpegPath = require('ffmpeg-static').path;
const child_process = require('child_process');
ffmpeg.setFfmpegPath(ffmpegPath);

const twitchStreamKey = 'your key goes here';
const rtmpServerAddr = `rtmp://live-dfw.twitch.tv/app/${twitchStreamKey}`;

function startFfmpeg(){
  let vid;
  if(running == 0){
    vid = child_process.spawn(ffmpegPath, [
      '-i', '-', // <-- This basically allows whatever written to stdin to be the input
      '-framerate', '60',  // <-- Depends on what framerate is being recorded
      '-vcodec', 'libx264', // <-- Video Codec if needed
      '-preset', 'ultrafast', // <-- Presets
      '-pix_fmt', 'yuyv422',  // <-- Helpful for dealing with non standard monitors etc
      '-bufsize', '1000k',  // <-- How big a buffer you want
      '-c:a', 'libmp3lame', // <-- depends on audio input
      '-f', 'flv', // <-- rtmp servers use flv as encoding this should be only encoding on outbound
      rtmpServerAddr
    ]);

    // onClose
    vid.on('close', (code, signal) => {
      console.log('FFmpeg child process closed, code ' + code + ', signal ' + signal);
      video.kill('SIGINT');
    });

    // onError
    vid.stdin.on('error', (e) => {
      console.log('Error froms STDIN', e);
    });

    // onData
    vid.stderr.on('data', (data) => {
      console.log('Data coming through STDERR:', data.toString());
    });

    // onWrite
    vid.stdin.on('write', (e)=>{
      console.log('something new was written', e);
    })

    running = 1;
    return vid;
  } else{
    return vid;
  }

}

let running = 0
let video;

function ffmpegProcess(e){
    if(running == 0){
      video = startFfmpeg();
    }
    if(running == 1){
      video.stdin.write(e); <-- This is where the video childProcess gets the buffer data
    }
}

module.exports = {
    ffmpegProcess
}

aperture.createBufferStream(ffmpegProcess)
Something like that would take advantage of the aperture performance benefits and ffmpeg wouldn't need to encode anything outside of what's required by the RTMP server.

We could definitely do this.

I think this is a great idea for another use of Aperture, but I'm not sure if it makes sense to add that functionality to Kap, since we describe it as a screen recorder. Feels like the UI to support that would be pretty unique and disconnected from the rest of the app. Unless we make it super simple, as in you select the area like you always do but when you click record it asks for the server info and starts streaming instead of recording (or maybe both?), without much extra customization
If we rework the plugin system for Kap 4.0, we can also keep something like this in mind as well

Any updates on this matter? Any support to stream to Youtube yet?

@uhlhosting https://blog.sindresorhus.com/issue-bumping-e3b9740e2a0

No matter how much professional you seem to be here, you just lost a user for all your apps.  Bleat!

@uhlhosting No need for personal attacks. I was not trying to be rude. Issue bumping is just not helpful and will not get this issue resolved faster. Kap is an open-source project we do for fun in our spare time. Streaming has just not been a priority as it's not something we personally need and it's also a large undertaking.
That being said, if anyone wants this, a good pull request is always welcome. That's the beauty of open-source.


Update input-color.json

It doesn't work for me in STP 63 (Tracking Safari 12.1) or Safari 12 beta(build 136<IP_ADDRESS>.2) on High Sierra. Is it maybe Mojave-only?

It should be partial then, not no support IDK what to say. Wait for official answer from @Fyrd so as to answer you since he may use STP. I don't have a mac computer, sorry

Mojave isn't released to the public yet, so it should be no.

Confirmed, looks like it was in an older build of TP but not seeing it now.

Why safari lags too much on HTML5 forms? No Datalist and No color input type now. Too bad. Edge and others have them too


Paladin Oath of Thunder can use Channel Divinity: Thunderous Rebuke event when they have no uses of Channel Divinity available

The Paladin Oath of Thunder 3rd level ability allows them to retaliate when struck in melee. This uses their Channel Divinity ability.
However, it appears that the game doesn't check that the Channel Divinity ability is available. Save game attached: just end turn (or heal), waiting for the goblins to inflict damage in melee.
Reaction is offered even though it has no uses left:

I finished the battle with -4 Channel Divinity available:

ThorChannelDivinityBug.zip

fixed. thanks for the save.


draft of first three labs

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

this was just a test of pull request


Provide API to retrieve an image's digest

I've just started using this library and while it works fine for most things, I haven't found a way to retrieve an image's digest. Would it be possible to add this functionality to the library?
Based on the API docs, the digest seems to be delivered in the Docker-Content-Digest header.

I've just seen that this can be accomplished as follows using the Client exposed by the library:
request, _ := http.NewRequest("HEAD", "https://registry-1.docker.io/v2/library/alpine/manifests/latest", nil)
request.Header.Add("Accept", "application/vnd.docker.distribution.manifest.v2+json")
response, _ := registry.Client.Do(request)
fmt.Println(response.Header["Docker-Content-Digest"][0])

However, I think it would still be nice if this functionality would be exposed by the library itself.

Was looking at this a few weeks ago myself. Came back to check and saw your comment. The Docker Manifest in the library would need to be changed to schema2. But I like how you dealt with it, my solution was dirtier :)

I've created a PR with this feature and manifest deletion: #21

Done in #21.


Jest test error

Bug report
Hi! When I try to write the test - I get the error
Summary
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Check the render method of `Schedule`.

Environment info
react-native info output:
System:
    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
    Memory: 321.80 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.16.2 - ~/.nvm/versions/node/v12.16.2/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v12.16.2/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.4 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 23, 25, 26, 27, 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-R | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>08749
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_231 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 2.1.0
Steps to reproduce
Just write a simple test
describe('Schedule screen', () => {
  test('Page must render correctly', () => {
    const { findByText, findByPlaceholder, debug, findByTestId } = render(
      <Schedule  navigation={navigation}/>
    );
  });
});

Reproducible sample code
const Schedule: React.FC<ISchedule> = ({ navigation }) => {
  const _onChangeSegmentControl = (
    event: NativeSyntheticEvent<NativeSegmentedControlIOSChangeEvent>,
  ) => {
    dispatch({
      type: ACTION_TYPES.SET_SELECTED_INDEX,
      payload: event.nativeEvent.selectedSegmentIndex,
    });
  };

  return (
    <SafeAreaView testID="Schedule.SafeAreaView" style={styles.container}>
      <SegmentedControl
        style={headerStyle.segmentContainer}
        fontStyle={headerStyle.segmentText}
        activeFontStyle={headerStyle.segmentActiveText}
        values={[
          t('for_days_segment_title'),
          t('week_segment_title'),
          t('month_segment_title'),
        ]}
        selectedIndex={state.selectedIndex}
        onChange={_onChangeSegmentControl}
      />
    </SafeAreaView>
  );
};

export default Schedule;

Any updates?

Are there any updates?

How are you importing your Schedule component into the test file? Since you're default exporting your component, you have to import it without brackets:
import Schedule from './Schedule';
You may be importing your component incorrectly:
import { Schedule } from './Schedule' (This won't work since you're default exporting the component)
Check the MDN docs if you need a more in-depth explanation:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import
Hopefully this helps!


EventEmitter2 is not handling throw exception and closing app

My expectation is that if an error is thrown within an event listener it should be handled by EE2 and  app will not be closed . or we will be able to handle using try catch ? So it is not the case here.
In EE node:events they use 'error' handler for this case
old ee examples:
ee.on('error', function (err) {
    console.log(err);
});

ee.on('some.other.event', async function () {
    throw Error('blah');
});

ee.emit('some.other.event');

Same issue here. But it seems to be possible to catch the error when we use emitAsync method.

Same issue here. But it seems to be possible to catch the error when we use emitAsync method.

same here. Could you please show me an example of how you manage to make it work with emitAsync ?

Same issue here. But it seems to be possible to catch the error when we use emitAsync method.

same here. Could you please show me an example of how you manage to make it work with emitAsync ?

Basically just doing a catch on your emitAsync call. It seems that with emitAsync is possible to catch errors, but with just emit isn't.
try {
    ee.emit("some.other.event");
} catch {
    console.log("catched!");
}
// Output: Error: blah

try {
    await ee.emitAsync("some.other.event");
} catch {
    console.log("catched!");
}
// Output: catched!

Oh, I have realized some tests here and identified that this problem only occours because the callback for some.other.event is a async function, but the emit have a sync behavior. So this problem is more about an unhandled Promise, not a bug at all.


Issue: UX, Functional: Last few lines of the editor are not accessible by user. Ads are placed on top of it.

Issue:

Goto: https://jsbin.com/
Click Javascript Tab.
Start Typing your code, Keep typing till the last line.
Once user reaches the last (last 2-3 lines) lines of the code, the code starts to hide behind the Ad banner.
Issue: Ad Banner blocks the view of last few lines of editor.

Tested On: Windows 10, Chrome Latest, Screen Resolution: 1920x1080

I just noticed the same Ads bar blocking the bottom navigation bar too. I access JSBin from ChromeBrowser in Android. Additionally, this same problem appeared mybe 1year ago and now it shows up again. Please help,


feat: classes of C⋆-algebras

This adds four classes of C⋆-algebras (unital / non-unital, commutative / noncommutative). We only allow for complex scalars, as the theory for real scalars, perhaps counterintuitively, depends on the theory for complex scalars.
For all existing CStarRing instances, we also include the appropriate CStarAlgebra instance (so long as it actually makes sense). The purpose of this is (a) to reduce typing and the size of variable statements, but also (b) to hopefully reduce burden on type class synthesis.
Note: we leave PartialOrder and StarOrderedRing unbundled from CStarAlgebra. This is because, even in the most common cases (e.g., ℂ), the partial order can be controversial as a global instance. Moreover, including it wouldn't match the literature (although this point is not in and of itself sufficient justification). So, if your statement about C⋆-algebras requires ≤, it is necessary to add these classes.

Closing in favor of #16953 to avoid a performance hit.


Abandoned?

Has this project been abandoned? There's no commit activity for 4 years...

Development has certainly slowed, and this particular repository is no longer being actively developed by the project. However, expect an announcement on https://commotionwireless.net soon!


  Can we consider tweak the tolerance a little bit?

Hi @Alicia1529 , there's a PR https://github.com/apache/incubator-mxnet/pull/18339 targeting to fix the failed CI edge job, let's hold on for a while and retry when it's get merged. Thanks.

Hi @Alicia1529 , https://github.com/apache/incubator-mxnet/pull/18375 which fixed the edge CI failure was merged in v1.x branch, please help to re-trigger the edge job, which should be passed now. Thanks.

@mxnet-bot run ci [edge]

Hi @ciyongch, this pr has passed all the tests and is ready to be merged.

Thanks @Alicia1529 , we get all the CI tests passed finally :)
@TaoLv @pengzhao-intel @leezu please help to take a look and merge it.


Update Control.js to allow custom control containers

This update allows a control to be added to the map even if it does not fall into one of the 4 control corner containers.
When a control is added without a defined corner container, the map will now append the control after the existing corner containers allowing for custom containers to be added to the map.

The point of this pull request is to allow custom controls which don't fit into one of the corners to still be added to the 'leaflet-control-container' div as a new container element inside the div instead of being randomly placed elsewhere in the DOM. This is important because it helps to keep the DOM organized, and keeps all of the controls in the same location so they all can be hidden/shown just by modifying their parent container element. I have begun to use this modification with map dialog popups where I want the temporary control positioned in the center of the map, I have been testing it with a modified version of leaflet-sidebar where instead of having the sidebar in the DOM after the map div, it is in the leaflet control container, and I have been using it for a crosshair control i use to add 'click' type functionality to the map for disabled users.
The benefits of keeping all of the controls in the control container is that it allows for the proper waterfall of events, and it makes maps with multiple controls function with less bugs.  For example, the leaflet-fullscreen plugin does not work with the leaflet-sidebar plugin because the leaflet-sidebar plugin is currently forced to be outside the leaflet map div in the DOM tree, so when the fullscreen plugin grabs the leaflet map container, it misses the sidebar. This same issue occurs with many other plugins where they are adding elements outside the leaflet-control-container, where they can cause conflicts with events not properly falling through to the map, or they are improperly using an existing control corner position for an element which should really not be in a corner position because it isn't in a corner.

I just want to keep nudging this idea forward, so here is an example of how a plugin could use this minor code tweak to better keep the DOM organized:

In the above example, using the modified code the sidebar div is now kept within the leaflet control container even though it does not fit in any of the control corners.
To me, this seems like an improved place for any/all of the custom controls / windows / floating dialog, etc which integrate into the map vs the following alternative where the sidebar is appended outside the map div even though it actually floats above the map on the screen:

Any thoughts?

I like the fundamental idea of having a anything goes controls container but I am finding this code confusing.
The code seems to be placing the new control directly under the control container. I would suggest for organization to have a container called "other-controls-container" as a child to the "leaflet-control-container" or something similar to that.
Also is there any CSS that is needed for this new set of controls? Or is the CSS in the local project file rather then the leaflet?
Can you provide an example of how a new control would be implement in this separate container?
Thanks

I also think this would be a valuable addition to adding leaflet controls with custom positions on the map. I disagree with the notion that they need to be separated from other controls.
Are there any plans of actually merging this or giving feedback? Because if not this should be closed considering it has been 2 years.