[Suggestion] Warn Kata users of forfeiting eligibility on "Solutions" tab of language that user has not completed before revealing solutions

Today, I have just realised that if a user completes a Kata in one language (which automatically brings you to the "Solution" tab of that language variant of said Kata) then choose another language in the Language Dropdown without first navigating back to "Details" or "Discourse", he/she immediately forfeits his/her eligibility of that language and views all the solutions for that language without any prior warning.  This has taken me by surprise when I completed a particular 6 kyu Kata in JavaScript, PHP and CoffeeScript (at different times all from either the "Details" or "Discourse" tab, so I did not accidentally forfeit my eligibility for any of these 3 languages), and then while I was still on the "Solutions" tab for CoffeeScript, I changed the language to "Python" expecting to see a message like "Solutions have been withheld".  Instead, I immediately saw all the relevant Python solutions and when I clicked "Train Again", the "Unlock Solutions" button was already set to "View Solutions" which I presume implies that I already forfeited my eligibility.
In this case, may you please add a warning message asking for the user's permission to proceed before eligibility for that language is forfeited and all solutions for that language are shown?  Thank you very much for your help and attention :smile:

Did you edit the kata first? That would have caused this.

Now I see :wink:  I presume that publishing a PHP translation to said Kata and having it approved would count as "editing the Kata"?

UPDATE: I have just tested this on a Kata I have not translated before and the "Solutions have been withheld" warning message appears as expected on languages I have not completed in so I guess this Issue can be closed now.  Thank you for your help and attention anyway :smile:


Tests for Kafka version 2.12-2.1.1 and 2.12-2.2.1

Would be nice if kafka-node can have more tests covering Kafka upwards versions and everyone would be more confident to use kafka-node with these versions. What do you think? @hyperlink


Custom error messages for env build

At the moment, a hard-coded error, saying 'an environment already exists with this name', will be thrown. We want this to be dynamic, showing the specific error of the problem.

The failure message is now passed through from the core.


Support APP_TOKEN for restrict all calls

https://github.com/unStatiK/tensoul-py-ng/commit/b6e7f97bcd2e421c7e1bb61b779ecd6d492c64f6


[flutter_releases] Flutter stable 3.3.7 Framework Cherrypicks

Flutter stable 3.3.7 Framework
Scheduled Cherrypicks

Merging. Plugins and customer testing are known failures.


fix theme

Fixes #
Changes

Import ThemeProvider from primer/react instead of styled-components

Checks

[x] Have you catchup your branch with the latest state in base?
[x] Have you lint your code locally prior to submission?
[x] Have you reviewed your proposed changes and removed debris?
[x] Have you successfully ran due tests with your changes?

Looks good to me!


fips: use tsan counter instead of tsan_add to increment

This change was required when merging to 3.0 (tsan_add doesn't exist there).
Might as well make the same change on master and 3.1 as well.
I'd forgotten about tsan_counter :cry:

[ ] documentation is added or updated
[ ] tests are added or updated

ping @openssl/committers for 2nd review

Add label for 3.0?

Ahh its already merged?

I had to apply this change as a fix when I merged the TSAN change to 3.0.
This PR is bringing 3.1 and master into line with what's in 3.0.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged, thanks for the reviews.


Holding a white cane when blind should let you feel more around you

Description

That's how it works in real life, so that's how it should work in-game, even if only slightly. It makes being blind slightly more tolerable and gives a proper reason to keep the item on you.
Though, something to mention is that the description of the item should also be changed if this gets added.

Blind people should be able to see footsteps and people's outlines when they talk. Or something like that.


Repo Works only with TommyChien/memorag-qwen2-7b-inst? Problems with Gated HF Models like Llama3

@qhjqhj00 the repo looks promising!
I am getting a HF auth error. I already got granted access to llama3.1 and I am using my HF token like below. I am using the 0.1.3 version.
from memorag import MemoRAG
from huggingface_hub import login

login(token=token_here, add_to_git_credential=True)

pipe = MemoRAG(
    mem_model_name_or_path="meta-llama/Meta-Llama-3.1-8B",
    ret_model_name_or_path="BAAI/bge-m3",
    beacon_ratio=16,
    load_in_4bit=True,
    enable_flash_attn=True,
    access_token='token_here'
)

However, I get this error (again, I already got access granted --my token has read-only properties):
Cannot access gated repo for url https://huggingface.co/meta-llama/Meta-Llama-3.1-8B/resolve/main/config.json.
Access to model meta-llama/Meta-Llama-3.1-8B is restricted. You must have access to it and be authenticated to access it. Please log in.

I decided to download the model directly from HF (using the same token) and it had no issue:
model_name = "meta-llama/Meta-Llama-3.1-8B"
local_dir = "./meta-llama-3.1-8b"
snapshot_download(repo_id=model_name, local_dir=local_dir, token=same_token)

However, I am not able to use this model as when I do:
pipe.memorize(small_part, save_dir="constitution/", print_stats=True)
I get the error:
AttributeError: 'LlamaForCausalLM' object has no attribute 'memory'
It just works with the TommyChien/memorag-qwen2-7b-inst or what am I missing here?

The issue is here, the argument should be access_token instead of token in memorag.py:
        self.model_kwargs = {
            "cache_dir": cache_dir,
            # "token": access_token,
            "access_token": access_token,
            "device_map": {"": device},
            "attn_implementation": attn_implementation,
            "torch_dtype": torch.bfloat16,
            "trust_remote_code": True,
        }

same for the tokenizer kwargs...
Hope that helps!

@qhjqhj00 had to reopen because: (btw, now I am using the latest memorag version)
ValueError: Cannot use apply_chat_template() because tokenizer.chat_template is not set and no template argument was passed! For information about writing templates and setting the tokenizer.chat_template

thanks for your comment, we would fix it in the next version!


Add Error Handling and Logging Statements

Issue Description
Enhancement Request: Add Error Handling and Logging Statements
Problem Statement
The current code lacks proper error handling and logging statements, which can make it difficult to diagnose issues and track the execution flow of the bot. Additionally, there is a need to include print statements to provide initial startup and status messages for the bot.
Proposed Solution
To address this issue, we need to add appropriate try-except blocks for error handling and logging statements to track the execution flow. Additionally, we can include print statements to provide meaningful startup and status messages for the bot.
Acceptance Criteria

Implement try-except blocks to handle potential exceptions and errors.
Include logging statements to track the execution flow, error messages, and important events.
Add print statements to provide initial startup and status messages for the bot.
Ensure the logging mechanism is configurable and follows best practices for log levels and formatting.

Technical Considerations

Identify critical sections of the code where exceptions can occur and wrap them in try-except blocks.
Utilize appropriate logging mechanisms, such as the Python logging module, to log important information, warnings, and errors.
Determine the desired log levels (e.g., DEBUG, INFO, ERROR) for different types of messages.
Consider implementing a centralized logging approach to consolidate logs from multiple components of the bot.
Place print statements strategically to provide essential information during startup and status updates.

Additional Information

The current code lacks try-except blocks and logging statements.
Including print statements will help provide informative startup and status messages.

Implementation Guidance
To implement this enhancement, the following steps can be considered:

Identify critical sections of the code where exceptions can occur.
Wrap those sections in try-except blocks to catch and handle potential exceptions.
Determine the appropriate logging mechanism for your bot, such as using the Python logging module.
Introduce logging statements at key points in the code to track the execution flow and important events.
Configure the logging mechanism to specify log levels, formatting, and log output destination (e.g., file, console).
Add print statements strategically to provide informative startup and status messages for the bot.
Test the code thoroughly to ensure proper error handling, logging functionality, and print statements.
Update documentation and code comments to reflect the changes made for error handling, logging, and print statements.

Please let me know if you need any further assistance or clarification regarding this enhancement request.

Solved in code refactorization.


Support Type1 Hint replacement

Actually we do not support Hint Replacement in type1 and just assume the font does not use it (this is not the cause of the strange hinting problems we see in the Tracemonkey paper).
This make the font in page 25 of http://faq.ktug.or.kr/wiki/uploads/MathFonts.pdf to fail to load (The sanitizer detects that an hstem is missing some parameters).
For more information see section 8.1, “Changing Hints Within a Character,” in Chapter 8, “Using Subroutines.” of the Type1 specification.

The issue with http://faq.ktug.or.kr/wiki/uploads/MathFonts.pdf font loading is not related to Type1 hint replacement. It looks the page 25 displays without any warning.
Commit 827d27ebf8bc9445bac4330b965c5b76e0151d51 provides the replacement/recalculation of type1 hint operators to type2. However the sanitizer rejects it due to http://code.google.com/p/ots/source/browse/trunk/src/cff_type2_charstring.cc?r=77#575

Looks like hint operators have no effect on the canvas font rendering. Tried on Mac OS and Windows.

I do not see any differences between Acrobat Reader and PDF.js on the last page.
Is the font load issue still exist ?

The sanitizer warnings are gone, there is a commit above that appears to have implemented this and the linked PDF renders without problems, so I'm going to close this as fixed. If we're missing support for something here, please open a new issue with more details and example files because currently this issue is not really actionable anymore.


Remove HeaderContentPresenter from All Controls

Describe the bug
Some controls ported from UWP still have the header content presenter. That convention was largely decided against for Avalonia and has been removed from other controls such as ComboBox recently.
We should go through all controls and remove it completely:

DatePicker
TimePicker
etc...

I'm making this a bug because the API is very inconsistent here.
Expected behavior
Avalonia controls should not have header content.
Additional context
There should be a separate HeaderContentPresenter control in any apps that need this functionality. The goal in Avalonia is not to flatten the visual tree and cause control-bloat like this.

@rabbitism I was planning on doing the Date/TimePicker. However, I havnt searched other controls yet and am not sure what others need updating. If you could look for other occurances of header in other controls and then fix those that would be a good way to split this up.

@rabbitism OK, there aren't that many then. If you want to update all three that's fine on my end. I certainly can use the time elsewhere.


New commits list

Very early WIP:

I will also re-work the commit badge, likely removing the "fancy" styling around it and just use icons to indicate signature. Part of the styling for it is unfortunately shared with last commit in file table, so extensive refactoring will be required to decouple those two ways of displaying a commit.

I think line dividers are still needed.

Will it ever get ready for review?

Maybe. It is pretty high on my list of things to do.

I think I'll first split out a PR that moves or removes the overly prominent styling of commits hashes, e.g. green/yellow/red for signature level. I think we should definitely subtemplate these which in turn will make the commit list implementation much simpler.

Not going to continue here, maybe later in a different PR, but anyone can feel free to pick this up in the meanwhile.


Fix : Commit statuses from forks are not included

can-merge was not fetching the commit statuses from forks, this PR addresses the issue.
There's no way in the github API that allows us to get those checks, only way to get the commit checks of a commit is by providing the original owner of the commit and then running the repository/search query.
As discussed with @ljharb  I started by modifying the buildQUery so that it return us the original author of the commit along with the commits.
In the runQuery.js i've added a new query that basically is similar to the repo query that we already use, and it calls the github api with the actual author of the commit, which returns us the commit checks. I then merge the two checks.
I've added this modification to just the search query for now, and can update it to work for the repo query as well after the reviews.🙂

The fork is deleted, so this and #72 are unrecoverable. I'll keep these open in case someone can resurrect anything out of it.

yay, turns out the fork was just private! i'll rebase this now.


feat: added second card

Hello Dan!

Hello Dan!
undefined

Hello Dan!
[object Object]

Hello Dan!
Hello! How can I assist you today?

Improvement:

The code diff shows that a new Card component has been added to the Home component but the import statement for the Card component has been removed. This may cause an error during compilation. The import statement should be added back as shown below:

import Card from './components/card'

The Home component is now rendering two Card components. It would be better to extract the two Card components into a separate component that can be reused across the application.

Improvement:

The pull request is adding a new card to the home page, which is great. However, it would be better to extract the new card into its own component to keep the code modular and reusable.

Code snippet for improvement:
// new component file named "NewCard.tsx"
import Card from './components/card'

interface Props {
  name: string;
}

export default function NewCard({ name }: Props) {
  return (
    <Card name={name} />
  );
}

// updated Home component
import NewCard from './components/NewCard';

export default function Home() {
  return (
    <>
      <Card name="John Doe" />
      <NewCard name="Jane Doe" />
    </>
  )
}

Use secrets in a more secure way, instead of using them directly in the workflow file, use Github's secrets feature to manage them and make sure that they are not exposed to unauthorized persons.
It is recommended to use relative imports over absolute imports as they are more scalable and easier to maintain.
When adding multiple elements to a component, it is recommended to use the map function instead of adding them one by one. This is more scalable and easier to maintain.

Code improvements:

Improve secrets handling by using Github's secrets feature.
Update the imports to use relative paths.
Use the map function to add multiple Card components.

import Card from '../components/card';

export default function Home() {
  const users = ["John Doe", "Jane Doe", "Bob Doe"];
  return (
    <>
      {users.map((user) => (
        <Card name={user} />
      ))}
    </>
  )
}

Improvement:

In the first code diff, the Comment on PR step can be improved by using the pull_request_review event instead of github-script to create a comment on the pull request. The pull_request_review event is triggered when a reviewer submits a review of the pull request.

Code snippet:
on:
  pull_request_review:
    types: [submitted]

jobs:
  job_name:
    runs-on: ubuntu-latest
    name: Job name
    steps:
      - name: Add a comment to the PR
        uses: actions/github-script@v6
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          script: |
            const { owner, repo } = context.repo;
            const { number } = context.payload.pull_request;
            const body = 'Hello World!';
            github.issues.createComment({ owner, repo, issue_number: number, body });

Improvement:

In the second code diff, the Home component can be improved by using a mapping function to create multiple Card components instead of hardcoding each one.

Code snippet:
import Card from './components/card'

export default function Home() {
  const names = ['John Doe', 'Jane Doe', 'Bob Doe'];
  return (
    <>
      {names.map((name) => (
        <Card key={name} name={name} />
      ))}
    </>
  );
}

/review

In the first code snippet, the step "Comment on PR" is removed. This step was responsible for adding a comment to the pull request. Consider adding a similar step in the new code snippet if this functionality is still required.

In the second code snippet, the import statements for Image and styles are removed. If these are required, consider adding them back.

In the second code snippet, the return statement now returns multiple Card components wrapped in a fragment. This is a good improvement as it reduces the number of render calls and simplifies the code.

/review

Improvement:

The code diff is adding new dependencies without explanation.
The code diff is also changing the number of Cards without explanation.

Code Snippet:
import Image from 'next/image'
import styles from './page.module.css'
import Card from './components/card'

export default function Home() {
  return (
    <>
      <Card name="John Doe" />
      <Card name="Jane Doe" />
      <Card name="Bob Doe" />
    </>
  )
}

/review

/review

Improvement:

In the pull_request job, the permissions specified in the jobs need to be moved to the top level permissions key outside of the job in order to make them global.
In the code diff, in the Home component, the import of Image and styles are unused and should be removed.
In the Home component, instead of rendering the Card component three times, we can map through an array of names and render the Card component for each name.

Updated Code snippets:
# Updated pull_request job
permissions:
  issues: write
  pull-requests: write
  contents: write
jobs:
  pr_agent_job:
    runs-on: ubuntu-latest
    name: Run pr agent on every pull request, respond to user comments
    steps:
      - name: PR Agent action step
        id: pragent
        uses: Codium-ai/pr-agent@main
        env:
          OPENAI_KEY: ${{ secrets.OPENAI_API_KEY }}
          GITHUB_TOKEN: ${{ secrets.TEST_ACTION_TOKEN }}
          API_TYPE: 'azure'
          API_VERSION: '2023-07-01-preview'
          API_BASE: '${{ secrets.AZURE_BASE_URL }}'
          OPENAI.DEPLOYMENT_ID: 'turbo301'
          CONFIG.MODEL: 'gpt-35-turbo'

# Updated Home component
import Card from './components/card'

export default function Home() {
  const names = ['John Doe', 'Jane Doe', 'Bob Doe'];
  return (
    <>
      {names.map((name) => (
        <Card key={name} name={name} />
      ))}
    </>
  );
}

/describe

Improvement: The PR includes unnecessary code changes.
Improvement: Instead of adding and removing code for the comment on PR step, it would be better to use an existing action like "actions/github-script" to create the comment.
Improvement: The code diff includes a new file "git-diff.sh" which is not necessary for this pull request.
Improvement: The Home component in the code diff should import the necessary components to avoid unused imports.
Code snippet for removing the comment on PR step and using "actions/github-script":
      - name: Comment on PR
        uses: actions/github-script@v6
        with:
          script: |
            github.rest.issues.createComment({
              issue_number: context.issue.number,
              owner: context.repo.owner,
              repo: context.repo.repo,
              body: 'Hello World!'
            })

Code snippet for importing only necessary components in Home component:
import Card from './components/card';

export default function Home() {
  return (
    <>
      <Card name="John Doe" />
      <Card name="Jane Doe" />
      <Card name="Bob Doe" />
    </>
  );
}

/review

/review

Improvement:

In the pull request job, add a step to comment on the pull request to notify the user about the status of the job.

Code snippet:
- name: Comment on PR
  uses: actions/github-script@v6
  with:
    script: |
      github.rest.issues.createComment({
        issue_number: context.issue.number,
        owner: context.repo.owner,
        repo: context.repo.repo,
        body: 'The PR job has completed successfully!'
      })

Improvement:

In the Home component, remove the unused imports.

Code snippet:
- import Image from 'next/image'
- import styles from './page.module.css'

Improvement:

In the Home component, refactor the return statement to use a map function to render the Card components.

Code snippet:
export default function Home() {
  const names = ['John Doe', 'Jane Doe', 'Bob Doe'];
  return (
    <>
      {names.map((name) => (
        <Card key={name} name={name} />
      ))}
    </>
  )
}

/review


webpage customization support added: annotationDiv customizationHook

@davidjamesbeck Two small changes:
ijalLine.py now inserts, after every translation line, an empty

.
text.py adds a comment line to the header

    <meta charset="UTF-8"/>

    <link rel = "stylesheet" type = "text/css" href = "ijal.css" />

I replace this comment, after building a page, using the venerable unix tool sed.  In my current work, this one line is replaced by these includes, which support the popup annotations:
<link rel="stylesheet" type="text/css" href="../pshannon.css" />

@davidjamesbeck  - Hi David,
Do you wish to review and merge this PR?  It should slide right in, having no conflicts.

Paul

Done. I’d run the tests and looked at the output days ago, but didn’t see it as a separate branch in my local repo for some reason.
Have you checked out webapp2_run_locally.py (dumb name, I know)? If I get a chance to make a new video tutorial soon, I’ll probably rechristen it webapp3.py and try it out on our VM
David
David

On Nov 26, 2019, at 6:28 PM, Paul Shannon<EMAIL_ADDRESS>wrote:
@davidjamesbeck https://github.com/davidjamesbeck - Hi David,
Do you wish to review and merge this PR? It should slide right in, having no conflicts.
Paul
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBQHVP7Q4NRJXYRHXG3QVXEKZA5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFH7DIY#issuecomment-558887331, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBVPNVYJ62EW45ZEB23QVXEKZANCNFSM4JQRGKBA.

@davidjamesbeck  Hi David,
Many thanks for the merge of the PR.
The new drag-and-drop is really very fine!  I   Good progress and error messages, and good resilience in the face of errors.  I dragged the Inferno sound file into the eaf dialog, my mistake was handled smoothly.   I know how much work lies behind smooth UI operations like this.  Bravo!
Maybe ijal.css is, in my copy of the repo, in the wrong place?   Here’s my rendered page:

Interesting. I didn’t have that happen on my computer, but the HTML in the iFrame should be calling the CSS packaged with the HTML and other output in the PROJECTS folder, and the app is supposed to copy ijal.css to there, so the setup in your repo shouldn’t matter. If you don’t get a copy in that directory, maybe there’s an order-of-operations thing. I’ll run it again tonight if I get a chance and see if I can replicate the error.
Another possibility is that cacheing problem we were running into way back when. I spent 3 extra hours testing this last update because the iFrame kept showing me only 2 lines of Inferno. It turned out that, because I used 2 lines only to save time while fixing up the drag-and-drop, that version of the text was in a cache somewhere and got used instead of the 4 line version I wanted to see for the final tests. That’s one reason the new code is so much cleaner—I went through line by line looking for a failure point, and was cleaning up as I went. Anyway, maybe if you empty the cache, quit the browser, and do it over, it will work?
David

On Nov 27, 2019, at 8:25 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
@davidjamesbeck Hi David,
Many thanks for the merge of the PR.
The new drag-and-drop is really very fine! I Good progress and error messages, and good resilience in the face of errors. I dragged the Inferno sound file into the eaf dialog, my mistake was handled smoothly. I know how much work lies behind smooth UI operations like this. Bravo!
Maybe ijal.css is, in my copy of the repo, in the wrong place? Here’s my rendered page:
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I just cloned the GitHub repo to my office computer and I’m getting the same thing. The ijal.css file is in the right place and the HTML displays correctly if I open the Inferno.html file in a browser directly, so the iFrame seems not to be using our stylesheet.  I wonder if adding the ijal.css styles to the styles for the web app would have any effect?
I really don’t like dcc.iFrame, not at all. :-(

On Nov 27, 2019, at 8:47 AM, David J Beck<EMAIL_ADDRESS>wrote:
Interesting. I didn’t have that happen on my computer, but the HTML in the iFrame should be calling the CSS packaged with the HTML and other output in the PROJECTS folder, and the app is supposed to copy ijal.css to there, so the setup in your repo shouldn’t matter. If you don’t get a copy in that directory, maybe there’s an order-of-operations thing. I’ll run it again tonight if I get a chance and see if I can replicate the error.
Another possibility is that cacheing problem we were running into way back when. I spent 3 extra hours testing this last update because the iFrame kept showing me only 2 lines of Inferno. It turned out that, because I used 2 lines only to save time while fixing up the drag-and-drop, that version of the text was in a cache somewhere and got used instead of the 4 line version I wanted to see for the final tests. That’s one reason the new code is so much cleaner—I went through line by line looking for a failure point, and was cleaning up as I went. Anyway, maybe if you empty the cache, quit the browser, and do it over, it will work?
David

On Nov 27, 2019, at 8:25 AM, Paul Shannon<EMAIL_ADDRESS>wrote:
@davidjamesbeck Hi David,
Many thanks for the merge of the PR.
The new drag-and-drop is really very fine! I Good progress and error messages, and good resilience in the face of errors. I dragged the Inferno sound file into the eaf dialog, my mistake was handled smoothly. I know how much work lies behind smooth UI operations like this. Bravo!
Maybe ijal.css is, in my copy of the repo, in the wrong place? Here’s my rendered page:
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I really don’t like dcc.iFrame, not at all. :-(

When using someone else’s library means we consent to their ontology, to their metaphysics: what the entities are, what operations are possible.   Sometimes those notions are - to use the old hacker term - manifestly brain dead.  Or at least that’s how it feels when things don’t work, make no sense, but (by our lights) ought to be straightforward.   “underdeveloped” is a kinder term.   Sorry for the pain!

Paul

Don’t be sorry, on the whole it is been pleasant and vastly educational. For all its quirks (which I am only sophisticated enough to perceive as “X is annoying for reasons I feel are not down to my incompetence”), Dash has given us the results we need with relatively little pain. I am actually hopeful it will develop, there seem to be users and people actively troubleshooting it. Let’s hope that we are only experiencing the pain of the early adopter (the “bleeding edge,” as a friend of mine put it).

On Nov 27, 2019, at 12:21 PM, Paul Shannon<EMAIL_ADDRESS>wrote:

I really don’t like dcc.iFrame, not at all. :-(

When using someone else’s library means we consent to their ontology, to their metaphysics: what the entities are, what operations are possible. Sometimes those notions are - to use the old hacker term - manifestly brain dead. Or at least that’s how it feels when things don’t work, make no sense, but (by our lights) ought to be straightforward. “underdeveloped” is a kinder term. Sorry for the pain!

Paul

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBWRXL5GOGFLL6XDPL3QV3CEVA5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKQLRQ#issuecomment-559220166, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBVDTP5L6SLLRLARI6DQV3CEVANCNFSM4JQRGKBA.

I think I’ve fixed this: I had altered the server route to only include “.html” files because I’d noticed the server route callback triggering multiple times, once for every file in the PROJECTS directory. I added “.css” to the accepted file suffixes and I see a properly formatted text in the iFrame on my home computer. You might want to pull the new webapp2_run_locally.py and try it out on yours as well.
David

On Nov 27, 2019, at 12:21 PM, Paul Shannon<EMAIL_ADDRESS>wrote:

I really don’t like dcc.iFrame, not at all. :-(

When using someone else’s library means we consent to their ontology, to their metaphysics: what the entities are, what operations are possible. Sometimes those notions are - to use the old hacker term - manifestly brain dead. Or at least that’s how it feels when things don’t work, make no sense, but (by our lights) ought to be straightforward. “underdeveloped” is a kinder term. Sorry for the pain!

Paul

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBWRXL5GOGFLL6XDPL3QV3CEVA5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKQLRQ#issuecomment-559220166, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBVDTP5L6SLLRLARI6DQV3CEVANCNFSM4JQRGKBA.

The revisions to webapp2_run_locally.py work - the iframed page displays just right!

Paul

On Nov 27, 2019, at 2:54 PM, David Beck<EMAIL_ADDRESS>wrote:
I think I’ve fixed this: I had altered the server route to only include “.html” files because I’d noticed the server route callback triggering multiple times, once for every file in the PROJECTS directory. I added “.css” to the accepted file suffixes and I see a properly formatted text in the iFrame on my home computer. You might want to pull the new webapp2_run_locally.py and try it out on yours as well.
David

On Nov 27, 2019, at 12:21 PM, Paul Shannon<EMAIL_ADDRESS>wrote:

I really don’t like dcc.iFrame, not at all. :-(

When using someone else’s library means we consent to their ontology, to their metaphysics: what the entities are, what operations are possible. Sometimes those notions are - to use the old hacker term - manifestly brain dead. Or at least that’s how it feels when things don’t work, make no sense, but (by our lights) ought to be straightforward. “underdeveloped” is a kinder term. Sorry for the pain!

Paul

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBWRXL5GOGFLL6XDPL3QV3CEVA5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKQLRQ#issuecomment-559220166, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBVDTP5L6SLLRLARI6DQV3CEVANCNFSM4JQRGKBA.

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

Woohoo!
Do you know what is going on with the server route callback exactly? Telling the webapp to fill the iFrame triggers that callback somehow, but I’m not sure why anything other than the HTML file is passed through it. Would it be because the HTML contains a link the ijal.css file?
David

On Nov 27, 2019, at 7:08 PM, Paul Shannon<EMAIL_ADDRESS>wrote:
The revisions to webapp2_run_locally.py work - the iframed page displays just right!

Paul

On Nov 27, 2019, at 2:54 PM, David Beck<EMAIL_ADDRESS>wrote:
I think I’ve fixed this: I had altered the server route to only include “.html” files because I’d noticed the server route callback triggering multiple times, once for every file in the PROJECTS directory. I added “.css” to the accepted file suffixes and I see a properly formatted text in the iFrame on my home computer. You might want to pull the new webapp2_run_locally.py and try it out on yours as well.
David

On Nov 27, 2019, at 12:21 PM, Paul Shannon<EMAIL_ADDRESS>wrote:

I really don’t like dcc.iFrame, not at all. :-(

When using someone else’s library means we consent to their ontology, to their metaphysics: what the entities are, what operations are possible. Sometimes those notions are - to use the old hacker term - manifestly brain dead. Or at least that’s how it feels when things don’t work, make no sense, but (by our lights) ought to be straightforward. “underdeveloped” is a kinder term. Sorry for the pain!

Paul

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBWRXL5GOGFLL6XDPL3QV3CEVA5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFKQLRQ#issuecomment-559220166, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBVDTP5L6SLLRLARI6DQV3CEVANCNFSM4JQRGKBA.

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

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBVRO3KCK4XVCW2F52LQV4RYZA5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFLGZ7A#issuecomment-559312124, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBRO5LWP7ZJOE4RHBN3QV4RYZANCNFSM4JQRGKBA.

would it be because the HTML contains a link the ijal.css file?

I think so.  That results in an http GET request which gets channeled through the specified flask route.   I think!

Paul

Ah. And the GET request is triggered when the iFrame tries to render the page?

On Nov 28, 2019, at 9:36 AM, Paul Shannon<EMAIL_ADDRESS>wrote:

would it be because the HTML contains a link the ijal.css file?

I think so. That results in an http GET request which gets channeled through the specified flask route. I think!

Paul

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBSAKEBVOLTQ2T5L43LQV7XR5A5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFNCGQY#issuecomment-559555395, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBQ6OVZK5GDTSHRC5Q3QV7XR5ANCNFSM4JQRGKBA.

I think so.  I imagine there is a route invoked for the iFrame, and then subsequent routes (back to the flask http server) for every request embedded in the iFrame HTML which resolves to the flask http server.

On Nov 28, 2019, at 8:44 AM, David Beck<EMAIL_ADDRESS>wrote:
Ah. And the GET request is triggered when the iFrame tries to render the page?

On Nov 28, 2019, at 9:36 AM, Paul Shannon<EMAIL_ADDRESS>wrote:

would it be because the HTML contains a link the ijal.css file?

I think so. That results in an http GET request which gets channeled through the specified flask route. I think!

Paul

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/paul-shannon/slexil/pull/53?email_source=notifications&email_token=AKN4HBSAKEBVOLTQ2T5L43LQV7XR5A5CNFSM4JQRGKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFNCGQY#issuecomment-559555395, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKN4HBQ6OVZK5GDTSHRC5Q3QV7XR5ANCNFSM4JQRGKBA.

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


Add decode-to-file function

Wraps decode and writes the hypotheses to a text file, or latex source file.

What's needed to get this completed?

The code I committed some time back which broke the interface: Just a wrapper to the decode function that then writes the returned text to a file. When I add it back in I'll just call it decode_to_file instead of decode.


checkov: 3.2.238 -> 3.2.239

Diff: https://github.com/bridgecrewio/checkov/compare/refs/tags/3.2.238...3.2.239
Changelog: https://github.com/bridgecrewio/checkov/releases/tag/3.2.239
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 338333 run on x86_64-linux 1

2 packages built:

checkov
checkov.dist


Package Addons for python3.7

Using the current docker image, we're unable to install / build TensorFlow in python3.7 with the following error:
ImportError: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /root/miniconda2/envs/py37/lib/python3.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so)

It seems like we need to compile using Ubuntu 16.04 libs, which will require a bump in the custom-op docker image. @yifeif would it be possible to bump the base image in the container? If so we can rebuild our release as 0.1.1 and include py37.
Alternatively, we could create a new docker image for builds.

@dynamicwebpaige Paige, tf-2.0-preview has supported python 3.7 in https://github.com/tensorflow/tensorflow/issues/25429 . Could you tell us how did you do it?

cc @gunan. Is ubuntu 14.04 being used for the build or some other docker image?

For python 3.7, we had to base our builders off of ubuntu 16.04.
Everything else uses ubuntu 14.04

We will definitely need a new image for python3.7.

Addons 0.2.0 has a py37 available on pypi

Bumping to ubuntu16+GCC5 caused issues issues as seen here in the most recent builds of TF:
https://github.com/tensorflow/tensorflow/issues/27067
This will remain unsoved until the manylinux2010 toolchain is finalized. See #119

What's the ETA for tf addons python 3.7 support?

@perfinion is there an updated build environment and date when TF pip packages will be built in it? Just for reference python 3.8 release is soon.

Looks like this is almost ready:
https://github.com/tensorflow/tensorflow/commit/ec83c8a8292aa881b701928a7ffbe2305cc0e4e5
@av8ramit Could you comment on the above question?

Ideally worst case within two weeks we will transition over. Waiting on one last issue with GPU custom ops.


the newest result

Hello guys.Thank you for your excellent work. I read the paper you updated and I found that the result is better than before.Can you share the codes that match the best result?
I  am waiting for your reply.

Hello,
In fact, the performance is improved by hyper-parameter tuning without any model change.
Specifically, alpha: 0.0002 -> 0.0005, r_act: 8 -> 9, r_bkg: 6 -> 4
You can also find it in the options.py.
In addition, I updated the best model file, with which you can see the improved result.
Thanks!

Thanks for your reply.I test the best model that you have updated. I have changed the parameter  as you said.But I can't  reproduce
the result.The result that I test is as follows:
Step: 0
Test_acc: 0.8905
average_mAP: 0.4038
<EMAIL_ADDRESS>0.6551
<EMAIL_ADDRESS>0.5836
<EMAIL_ADDRESS>0.5052
<EMAIL_ADDRESS>0.4158
<EMAIL_ADDRESS>0.3245
<EMAIL_ADDRESS>0.2266
<EMAIL_ADDRESS>0.1161
Do you know the reason?

Hello,
In fact, the performance is improved by hyper-parameter tuning without any model change.
Specifically, alpha: 0.0002 -> 0.0005, r_act: 8 -> 9, r_bkg: 6 -> 4
You can also find it in the options.py.
In addition, I updated the best model file, with which you can see the improved result.
Thanks!

Thanks for your reply.I test the best model that you have updated. I have changed the parameter as you said.But I can't reproduce the result.The result that I test is as follows:
Step: 0
Test_acc: 0.8905
average_mAP: 0.4038
<EMAIL_ADDRESS>0.6551
<EMAIL_ADDRESS>0.5836
<EMAIL_ADDRESS>0.5052
<EMAIL_ADDRESS>0.4158
<EMAIL_ADDRESS>0.3245
<EMAIL_ADDRESS>0.2266
<EMAIL_ADDRESS>0.1161
Do you know the reason?


feat: add a BatchQuery RPC method

Github issue: https://github.com/xmtp-labs/hq/issues/899
This change introduces the concept of batch queries, which provide no-frills bundling of existing QueryRequests and QueryResponses.
Implementation details (parallelism, batch size limits) are omitted from the proto API and are left as implementation choices.

Shoot, my proto version is slightly off which leads to a much larger diff set. I can lock and regen if that is preferable.

Shoot, my proto version is slightly off which leads to a much larger diff set. I can lock and regen if that is preferable.

Yes please. I'm hoping to sneak in a little project to standardize our proto compiler into a Docker image some time in the next few months, but until then synchronizing versions is best.

@neekolas - I got the versions right but still a large diff. Some of those look expected, but do any of those diffs look out of place? The new line + // are a bit suspicious but not sure what causes those.

Odd that you are still getting diffs even with the versions matching, but they all seem related to an extra line of comments in the generated code, which doesn't matter.
:shipit:

Ran e2e tests referencing github.com/xmtp/proto/v3 v3.11.1-0.20230104230713-55e48609f0dd and they passed, going to merge.


version error

Hello,
I get the following error message when installing Docker using the script.
INFO: Searching repository for VERSION '10'
INFO: apt-cache madison docker-ce | grep '10' | head -1 | awk '{$1=$1};1' | cut -d' ' -f 3
ERROR: '10' not found amongst apt-cache madison results"

The following is displayed when I execute the command Manuel:
apt-cache madison docker-ce
 docker-ce | 5:26.1.1-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:26.1.0-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:26.0.2-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:26.0.1-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:26.0.0-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:25.0.5-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:25.0.4-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:25.0.3-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:25.0.2-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:25.0.1-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:25.0.0-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.9-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.8-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.7-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.6-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.5-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.4-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.3-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.2-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.1-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:24.0.0-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:23.0.6-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:23.0.5-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:23.0.4-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:23.0.3-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:23.0.2-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:23.0.1-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
 docker-ce | 5:23.0.0-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages

The operating system is a freshly installed Debian 12.
Perhaps you have an idea why this could be the case.
If further information are needed please do not hesitate to ask.

I suspect that the environment you're running the script in has a $VERSION environment variable set. The install script allows a VERSION to be specified to install a version of the packages other than "latest". It's a bit unfortunate that the script chose to use VERSION for this, as it's a rather generic name for the environment-variable, so it's possible that it collides with something else having set an environment variable with that name.
In either case; if the VERSION variable is set to some version that doesn't exist, the script will fail here; https://github.com/docker/docker-install/blob/dd4d114074ecd649c37aa17e688c55fbd4c032fb/install.sh#L509-L517
Here's an example to reproduce this;
curl -fsSL https://get.docker.com > install.sh
export VERSION=10
sh ./install.sh

# INFO: Searching repository for VERSION '10'
# INFO: apt-cache madison docker-ce | grep '10' | head -1 | awk '{$1=$1};1' | cut -d' ' -f 3
#
# ERROR: '10' not found amongst apt-cache madison results

If you didn't intend installing a specific version, you can unset the environment variable (unset VERSION), or unset it for just the installation (env -u VERSION <command to run>);
printenv VERSION
# 10

env -u VERSION sh ./install.sh
# Executing docker install script, commit: 6d9743e9656cc56f699a64800b098d5ea5a60020
# + sh -c apt-get update -qq >/dev/null
# ...

Based on the above, I don't think there's a bug at hand, so I'll close this ticket, but I hope the above helps you (and others arriving here).


Fix zeah hot cold dig locations

This would close #3708 and #3713.

Each of the commits references those issues


python3Packages.prayer-times-calculator: init at 0.0.4

Motivation for this change
Python client for the Prayer Times API
https://github.com/uchagani/prayer-times-calculator
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123151 run on x86_64-linux 1

1 package failed to build:

home-assistant

2 packages built:

python38Packages.prayer-times-calculator
python39Packages.prayer-times-calculator

Result of nixpkgs-review pr 123151 at 7ddf7637 run on x86_64-linux 1

1 package failed to build:

home-assistant

2 packages built successfully:

python38Packages.prayer-times-calculator
python39Packages.prayer-times-calculator

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Failures are only actionable with logs, so here we are again.

Result of nixpkgs-review pr 123151 run on x86_64-linux 1

3 packages built:

home-assistant
python38Packages.prayer-times-calculator
python39Packages.prayer-times-calculator


Would be possible to store data in a file or call it by another code?

It works well. Would be possible to store data in a file or call it by another code?

Sorry, my bad. my question was How to place the TS imported data inside DataFrame instead of plotting?


List command problem

Evey option I try with the list command fails with 'no gd context is found; use gd init'. It did work earlier in the day, pull and push both work, I have tried init several times and there is no difference. Is some magic required ?
regards CB

You have to be within the folder that you mounted your drive ie where your credentials are.

It works there, I think a modification of the README might save some angst, it shows path1 and path2 syntax just the same as pull and push. Possibly highlight  that the init command appears to have an odd path syntax as well.
CB

Remember that list is for remote listing so typically if you have a path in remote you can do:
drive list -d -1 path
OR
drive list -d -1 path1 path2 path3
OR
drive list -d -1 // The path will be resolved relative to the current working directory.

@CountryBumkin feel free to submit a PR.

@CountryBumkin drive init is what creates a drive context, you can't have one without init.


save cost on CI: use a bit low/cheap ec2 instance type on running testing suite. build still use high ec2 on build proton.

Describe what enhancement you'd like to have
as titled:
save cost on CI: use a bit low/cheap ec2 instance type on running testing suite. build still use high ec2 on build proton.

if anyone wanna dive into ,plz detailed check every place we use
      ec2-instance-type: ${{ vars.X64_INSTANCE_TYPE }}


Is there any way to create a us_timer for custom use?

Yes. Loop::get() returns a Loop * but all pointers are convertible to their uSockets counterpart. So Loop * is convertible to us_loop_t * and from that you can us_create_timer

THX


about the log(Ls) in Table 2

So sorry to bother you .  I have a little bit of trouble calculating the   log(Ls) of various methods in Table 2. The logarithm of the loss with covariance matrix is always negative, and the absolute value is greatly different from the paper. Would it be possible for you to share the evaluation code you used to computer the log(Ls) in the Table 2?  Thank you very much for your help.

Sorry, I'm not an author of this paper. Please contact the authors for your questions about the paper.


Converted AuthContainer to typescript, updated staticStorageSlot to s…

…upport the reset operation (to use useStore)
Jira Ticket: https://broadworkbench.atlassian.net/browse/ID-798
Summary of changes:

AuthContainer.js -> AuthContainer.ts
Updated staticStorage slot to support reset

Why

More clarity on code related to auth, which will help with ID-720.

Currently running into this issue. Does not appear to be breaking, but it seems to think that "children" is being used as a prop.


Get number of bytes written/read?

Could the serialize_into and deserialize_from methods return the number of bytes written/read respectively? This would both handy and more efficient, since you already have to compute these values in these methods, and it thus saves an extra call to serialized_size.

Hmm, on second though, I'm not sure how easy this is to add to code.

If you use the structs defined here to do the deserialization you can grab the number of bytes read.
By using the function encoded_size, you can get the size of the struct as it would be on the wire.

It doesn't seem to be documented how to use those structs directly.

I've added documentation to rustc-serizlize DecoderReader and serde Deserializer.  The encoded_size and serialized_size functions are already documented.

Thanks for this. That’s quite handy.
Not sure if it bothers you, but there’s a typo in the docs – “bytes_red”. Otherwise good.

On 8 Feb 2016, at 01:36, Ty Overby<EMAIL_ADDRESS>wrote:
I've added documentation to rustc-serizlize DecoderReader http://tyoverby.com/bincode/bincode/rustc_serialize/struct.DecoderReader.html and serde Deserializer http://tyoverby.com/bincode/bincode/serde/struct.Deserializer.html. The encoded_size and serialized_size functions are already documented.
—
Reply to this email directly or view it on GitHub https://github.com/TyOverby/bincode/issues/54#issuecomment-181154949.

aah!  Thanks!


Can the alarm content be customized？

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Can the alarm content be customized？
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.10
💻 Operating System and Arch
Centos 7
🌐 Browser
Edge
🐋 Docker Version
No response
🟩 NodeJS Version
No response

What notification provider are you using?

Templating for most notfication providers has not been implemented.
See https://github.com/louislam/uptime-kuma/issues/646
The webhook and smtp notifications are support templating.

您使用的是哪个通知提供程序？

feishu


Tuning Oscillators

Great work, really interested to see where this goes 👍
If you have a patch with two or three VCOs, how would you denote them being tuned or detuned? Or tuned an octave up or down?

Also with a VCO you might have a Coarse and Fine knob, but I guess you're just setting the Freq.
So maybe you would have...

VCO 1: Freq = 65.41 Hz

VCO 2: Freq = 65 Hz

VCO 3: Freq = 98 Hz

That's exactly what I was thinking. You'd also have the option to write the knob position as a percentage but I guess that wouldn't be too reliable in that case.

Yeah, that makes sense :)


Allow Placeholders to form part of sorting keys

Duplicated from discord:
Add a way to sort players in the tablist in alphabetical order of placeholders (Feature that has TAB by NIEZNANY).
Will be highly appreciated and is so powerful in different ways. We sort players by their clan name (placeholder) (so players in the same clan are displayed together it the TAB)

yep, throwing another please into the pile lol. A plugin that does this is bungee tab list plus, on the off chance the code is helpful. https://github.com/CodeCrafter47/BungeeTabListPlus/

Probably the solution would be changing the way that you specify the sorting key to accept a string and just build in the role weight thing as a placeholder

Added with https://github.com/WiIIiam278/Velocitab/pull/94


laravel-mix not found

I've been completely unable to get this to work. Just keep getting the following.
sh: laravel-mix: command not found

npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/bin/node" "/Users/username/.npm-packages/bin/npm" "run" "dev"
npm ERR! node v7.4.0
npm ERR! npm  v4.1.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! my_site@ dev: `laravel-mix`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the my_site@ dev script 'laravel-mix'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the my_site package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     laravel-mix
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cinder
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls my_site
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/username/Sites/laravel_sites/my_site/npm-debug.log

Node and Npm are at latest versions and laravel-mix is definitely there.
I've tried this on a fresh install of Laravel too but get the following:
npm ERR! Darwin 16.4.0
npm ERR! argv "/usr/local/bin/node" "/Users/username/.npm-packages/bin/npm" "run" "dev"
npm ERR! node v7.4.0
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! @ dev: `node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the @ dev script 'node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/username/Sites/laravel_sites/my_new_site/npm-debug.log

This may very well not be a but and just something I'm doing wrong but I've noticed a couple of similar problems happening for people.
Thanks

You could try the following:
Ececute this code in your project root directory
npm init -y
npm install laravel-mix --save-dev
cp -r node_modules/laravel-mix/setup/** ./
So now you shoudl also have an webpack.config.js in your project root.
Now try to run
npm run [SCRIPTNAME] e.g. npm run dev

You can also visit: GitHub - laravel-mix - Installation
This should fix most of the problems u could run into :)

Great thanks I'll give that a go :)


Jonmv/paginate search results

@freva or @ldalves please review and merge.

PTAL.

Great! RE: OffsetPagination, move it to own file under App/shared/components/ and re-use in article view?

That isn't based on offset, though. It's an array of IDs to look up. Only the four nulls would be reused.

Done. Also added side margins to align with below text — you'll be happy to know the required amount was then reduced to 0.32em, since I'm lazy and used a single margin attribute. for all four.


python311Packages.aiocomelit: 0.3.1 -> 0.5.0

Diff: https://github.com/chemelli74/aiocomelit/compare/refs/tags/v0.3.1...v0.5.0
Changelog: https://github.com/chemelli74/aiocomelit/blob/0.5.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 267028 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.comelit
python310Packages.aiocomelit
python310Packages.aiocomelit.dist
python311Packages.aiocomelit
python311Packages.aiocomelit.dist


Document Tabs

This PR adds documentation for tabs.
@pbugnion I would be particularly interested if you could take a look at the modifications in helpers.py, I had to pass some module imports into exec in order to get the callbacks to work, previously it was complaining about dbc not being recognised etc. What I've got works, but there may be better ways to do it.

I think this looks great! I've made a couple of comments inline, specially around helpers.

Thanks for the review @pbugnion! I agree that we should be careful to keep snippets relatively self-contained. I'll take another look at the load_source_with_app function and implement your suggestions.

@pbugnion this is now ready for another review
The main outstanding question I have is on naming. The function name load_source_with_locals doesn't quite sit right with its argument globals_dict which takes its name from exec's globals parameter. Any preference on how best to resolve? Or whether you think there is anything to resolve?

I was originally thinking of passing the variables as locals to exec, not globals, hence the name. According to the docstring on exec, though:

The globals must be a dictionary and locals can be any mapping,
defaulting to the current globals and locals.
If only globals is given, locals defaults to it.

Thus, we can't pass just locals. I think we should just rename the function to load_source_with_globals, or load_source_with_environment?

I actually tried something very similar to this originally, and checked the above snippet just to be sure, but if you do that the documentation page for tabs throws a name error saying tab1_content is not defined. For a reason I haven't been able to figure out yet that needs to be passed to globals in exec to work. In which case would the best thing be to pass everything in to globals, leave the current implementation more or less as is but rename to load_source_with_environment as suggested in a previous comment?

Ah that makes sense. Not sure why it's not working, but my understanding of exec is fairly limited.

In which case would the best thing be to pass everything in to globals, leave the current implementation more or less as is but rename to load_source_with_environment as suggested in a previous comment?

I think that make sense, yes.
Thanks for tackling this!

This looks perfect, thank you!


Cannot find module 'fs'

I have an app created with electron-forge trying to utilize  electron-redux v1.5.4. I'm also using @reduxjs/toolkit
I have implented my mainRenderer and storeRenderer in the manner described in the readme file, adjusted for @reduxjs/toolkit
mainStore.js
import { configureStore } from "@reduxjs/toolkit";
import appReducer from "./appSlice";
import {
  forwardToRenderer,
  triggerAlias,
  replayActionMain,
} from "electron-redux";

const configureMainStore = () => {
  const store = configureStore({
    reducer:  appReducer,
    middleware: (getDefaultMiddleware) => getDefaultMiddleware().concat(forwardToRenderer),
  });

  replayActionMain(store);

  return store;
};

export default configureMainStore;

rendererStore.js
import { configureStore } from '@reduxjs/toolkit';
import appReducer from './appSlice';
import { forwardToMain, replayActionRenderer, getInitialStateRenderer  } from 'electron-redux';

const configureRendererStore = () => {
  const initialState = getInitialStateRenderer();

  const defaultMiddleWare = get

  const store = configureStore({
      reducer: appReducer ,
      initialState: initialState,
      middleware: (getDefaultMiddleware) => getDefaultMiddleware().unshift(forwardToMain)
    });

  replayActionRenderer(store);

  return store;
}

export default configureRendererStore;

When I run compiling the Renderer Code I get the following error:
ModuleNotFoundError: Module not found: Error: Can't resolve 'fs' in 'C:\MyDev\AirFarmer\node_modules\electron',
The chrome window gives a bit more detail:
Uncaught Error: Cannot find module 'fs'
    at webpackMissingModule (index.js?bdb9:1)
    at eval (index.js?bdb9:1)
    at Object../node_modules/electron/index.js (index.js:2259)
    at __webpack_require__ (index.js:4332)
    at fn (index.js:4543)
    at eval (forwardToMain.js?74c1:8)
    at Object../node_modules/electron-redux/dist/middleware/forwardToMain.js (index.js:2216)
    at __webpack_require__ (index.js:4332)
    at fn (index.js:4543)
    at eval (index.js?78f6:71)

I've read this is related to webpack v5+
had a similar issue with "path" which I was able to solve with by updating the webpack.render.config:
module.exports = {
  // Put your normal webpack config below here
  module: {
    rules,
  },
  resolve: {
    fallback: {
      path: require.resolve("path-browserify"),
    },
  }
};

I've tried lots of things already including setting nodeIntegration: true in webPreferences when creating the browser window.
Has anybody else experienced this? Does anybody have a solution?
Thanks
UPDATE - Still an issue
The cause is that "forwardToMain.js" has require("electron"); , which in turn requires 'fs'.

Facing exact issue, any luck with solution?

Hi @MohitDeshwal, I did get past this in the end, but it required a change in my plan on how to manage state in my electron app, rather than getting what I was trying to do working (Which I now think never would have).
The current security recommendations for electron(https://www.electronjs.org/docs/latest/tutorial/security) point 3 (Enable context isolation in all renderers that display remote content) means you won't be able to utilize a state synching package like 'electron-redux' if you have contextIsolation set to true. You will not be able to utilize any Electron internals in your rendering process.
For my project, I just stopped trying to sync state between renderer and main (using electron-redux) - in the main process I don't have redux, I only use redux in my renderer process.
In places where I need data from main process in state I just expose a method in my preload script using contextBridge, when the render process gets it's response, I stuff it into state then.
https://docs.w3cub.com/electron/tutorial/context-isolation  This site here has some starter info on setting up your contextBridge


[Bug] Houkai3rd cannot be executed

Description
The game does not start due to a DLL error.
Reproduction Steps

Install
cannot be executed (dll error)

Expected Behavior
No response
Screenshots
No response
Starward Version
0.8.2
Windows Version
Windows 11 (22H2) build 22621.1928
Log
No response
Additional Context
No response

Sorry, you didn't provide any useful information, so I couldn't help you.

Have you installed DirectX yet? Some DLL errors are usually caused by not having DirectX installed.

I think I have fixed this issue bdb67f763f83bc7f6d0a0af9e87afde74305717f, and you could test it in the next game update.

thx


core: chat_* docstrings

Added missed docstrings. Formatted docstrings to the consistent form.

@eyurtsev Thanks!


Vite: is there a way to import files in .css.ts files?

Currently importing an image fails with this error:
[plugin:vanilla-extract] Build failed with 1 error:
Check.css.ts:6:16: error: No loader is configured for ".png" files: pic.png

, even though it works fine in a regular .ts file.

.css.ts is working fine on my end with latest vite version. Try
export default defineConfig({
  assetsInclude: ['**/*.png'],
  ...
})

This is probably because Vanilla Extract runs .css.ts files in esbuild to generate the stylesheets, regardless of which plugin you use. There is currently no way to add loaders or configure esbuild here. Curious what your use case is?

@dkzlv Makes sense. I think having the ability to configure esbuild would be a good addition, it would also be a better way of doing this: https://github.com/seek-oss/vanilla-extract/pull/661

I believe this is also a problem with importing font files (.woff2) in your VE files. Maybe we can consider adding support for url imports (images, font files) to the default config.

Yeah I'm trying use static assets in my CSS, such as for a custom <li> bullet style, but we're facing the same limitation.
import { style } from "@vanilla-extract/css";

import myIcon from '../assets/icons/MyIcon.svg'

export const myListItem = style({
    listStyle: `url(${myIcon})`,
})

[plugin:vanilla-extract] Build failed with 1 error:
src/components/MyComponent.css.ts:6:25: error: No loader is configured for ".svg" files: src/assets/icons/MyIcon.svg

Is this something we can get working with some tweaking of esbuild?

Is there something the community can help with here? It's not possible to use a file loader right now because it requires defining the outDir for esbuild, which isn't exposed in the current esbuild options.

Made a simple plugin that fixes this
https://github.com/wobsoriano/esbuild-vanilla-image-loader
import { vanillaExtractPlugin } from '@vanilla-extract/vite-plugin'
import { ImageLoader } from 'esbuild-vanilla-image-loader'

export default defineConfig({
  plugins: [
    vanillaExtractPlugin({
      esbuildOptions: {
        plugins: [ImageLoader()],
      }
    }),
  ],
})

@wobsoriano Works perfectly! Awesome job

I ran into this same issue as well (using Vite) - I have a bunch of custom cursors (pngs). What I ended up doing is putting all the cursors in their own stylesheet that uses CSS modules rather than vanilla extract. It's an ugly hack but at least I'm unblocked.
I tried the plugin and couldn't get it to work - the url that it produced had the wrong path.

I'm using Solid-Start, If I directly write relative paths in url(), it's not handled by vanilla-extract, but will be handled by vite itself! (I guess when vanilla-extract gives the generated CSS to vite)

Run npm run build:

The issue is that vanilla-extract inserts a wrong style sheet in development mode:

It overrides the correct property below

@dkzlv This issues seems solved by the addition of esbuildOptions to the esbuild, vite and rollup plugins. The docs were missing for vite and rollup, but I've added that in #1120.

Why would we not want this to be dealt with automatically in all vanilla extract integrations? Referencing assets from css files is a very normal workflow. Adding extra plugins just to support assets like svgs, images, font files, etc. is a pretty annoying extra overhead to have to deal with.

I've thought about this issue some more, and I suggest re-opening this issue! Here's why:
First off, I do think it's a good idea for vanilla-extract to be abstracted away from the bundler of choice. The bundler is after all responsible for assets, since it's part of the bundling process, so expecting it to be handled out of the box is a bit unfair. However, we can't ignore the fact that it's incredibly common to reference things like images and fonts in css files, and since .css.ts files are supposed to simply be a typesafe variant of css files, why should that workflow not also be possible, and  typesafe?
I see two things missing: A: documentation, B: integration configuration options
Documentation
Nowhere in the docs is there any mention of the limitations explored in this github issue. There's even no information on how to simply import assets in .css.ts files, which I think is very surprising considering how common of a workflow that is.
At the very least I would expect a section in the docs explaining this caveat so it's more visible to new users, and even better provide some examples on how you can implement asset support in .css.ts files, preferably one example per integration.
Integration configuration options
As mentioned in this thread, esbuildOptions allow us to extend esbuild to support asset imports, even if it requires some heavy tinkering. The problem is this isn't consistent across all integrations. I've tried to do the same thing with webpack, but was not able to because some configuration options are missing. I don't know about the rest of our integrations. I think this kind of caveat would also be worth mentioning in the docs, but more importantly it begs the question, do we not want to improve this? I think it would be great if we could make each vanilla-extract integration configurable enough to support importing assets, preferably even adding test cases to ensure this common workflow is possible in all integrations.


What does the 'healthCheckPath' actually mean in consul discovery

I am testing out the Consul Discovery. And i see the document said the consul:discovery:healthCheckPath setting is server health check path, we can set the setting to provide our own health check. So i set this setting in my sample project:
  "Consul": {
    "Host": "localhost",
    "Port": 8500,
    "Discovery": {
      "ServiceName": "Test",
      "HealthCheckPath": "/health",
      "Port": 5000
    }
  }

And in my sample project startup, I config the health check endpoint by Microsoft.Extensions.Diagnostics.HealthChecks packages:
services.AddHealthChecks()
    .AddCheck("self", () => HealthCheckResult.Healthy());

....

app.UseEndpoints(endpoints =>
{
    endpoints.MapControllers();
    endpoints.MapHealthChecks("/health");
});

But when i started the project, I can't see the consul detect the /health endpoint. Even i change the health check result to unhealthy, The service check in consul still be passed. So i'm confused the setting,  And want to know how to config the health check for consul discovery  use

HealthCheckPath means the stem of the url off the HostName (defaults to machine name) so running locally on windows machine the healthcheckUrl becomes   http://desktop-1jnk1hq:5000/health. So your assumption is correct.
The reason the configuration wasnt working as expected was because by default Consul Configuration is using TTL controlled by "consul:Discovery:Heartbeat:Enabled" which is true.
In order to use actuator or Msft Health checks, you need something like this.
"consul": {
    "Host": "localhost",
    "Port": 8500,
    "Discovery": {
      "Heartbeat": {
        "Enabled": "false"
      },
      "HostName": "host.docker.internal",
      "ServiceName": "Test1235",
      "HealthCheckPath": "/health",
      "Port": 5000
    }
  }

In addition it helps in the consul ui to see the healthcheck type being used ex. TTL or HTTP. You want it to be HTTP and the note below has helpful error messages while trying to reach the health check endpoint.

Let me know if you have any more questions.

@hananiel Thanks! It's worked

@hananiel  Thank for the great clearification. It worked based in your suggestion..


Example not valid with the upcoming .NET 5

TFM for .NET 5 will be net5.0 (see https://devblogs.microsoft.com/dotnet/announcing-net-5-preview-4-and-our-journey-to-one-net/). Using this condition will probably break things when porting projects to .NET 5 as it is more similar to .NET Core than .NET Framework.

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

ID: 378f740b-d567-135e-0de9-a3cbd311b2dd
Version Independent ID: ff69814c-8600-f24a-530e-9a219bd6d8de
Content: MSBuild Conditions - Visual Studio
Content Source: docs/msbuild/msbuild-conditions.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @ghogen
Microsoft Alias: ghogen

@jairbubbles -- thank you for your feedback.  Please clarify your issue.  Are you referring to this condition?

<PropertyGroup Condition="'$(TargetFramework.TrimEnd(`0123456789.`))' == 'net'">

Yes! I think removing the trimming of . should fix it.


BUG: indices or aliases with a @ can't be queried

I have indices with an @ in the name but I can't query them as I get this error:

Hi @JeroenTriptic got it, for now the parser not support @, I will implement it in next release version, Thanks your feedback.

Hi @JeroenTriptic  please try the latest version: v1.10.3, and also you can download from Jetbrains market v1.10.3
Thanks your feedback, If you meet any issue please let me know.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3163

Questions ?
Please refer to the Backport tool documentation


Error kernel.cu 2523 on dynexsolvevs v2.2.3

i'm getting this error on win10 64bit with nvidia gtx 1050ti:
[BLOCKCHAIN] STARTING DYNEXSOLVE SERVICE
GPUassert: the launch timed out and was terminated c:/DYNEX/DynexSolve/DynexSolveVS/DynexSolveVS/kernel.cu 2523
this phat doesnt exists!

any update ? I meet the same issue...

No, No Activity and No solution! 🤔🤨☹

update to 2.2.5 miner...
https://github.com/dynexcoin/Dynex/releases

someone know that following issue ?
"GPU assert: out of memory C:/DYNEX/DynexSolve/DynexSolveVS/DynexSolveVS/kernel.cu 1171"
4 similar RTX 3090 -> If I disable one GPU, then it start to mine without error
thx

Obsolete by now


HDDS-8411. Show the total number of CLOSING, QUASI_CLOSED, CLOSED, DELETING Containers in Recon

What changes were proposed in this pull request?
This PR adds additional container information to Recon, which shows the total count of containers in some states, including CLOSING, QUASI_CLOSED, CLOSED, and DELETING.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8411
How was this patch tested?
Unit test

/pending


Module 'types' not found in CircuitPython 7.1.0

adafruit_requests.py, version 1.10.3+ imports module 'types' which is not defined in CircuitPython 7.1.0:
ImportError: no module named 'types'

This is fixed by https://github.com/adafruit/Adafruit_CircuitPython_Requests/releases/tag/1.10.4, which will be in the bundle tonight.

Confirmed with pyportal and install from today's bundle this is resolved.

thankya!


[5.8] Multiple universal email recipients

When testing email there is currently an option to set a universal to address. It only supports having one recipient. Sometimes it may be helpful to be able to send to multiple recipients if you have multiple email addresses using different email clients. This way you can easily see the results in each email client without having to forward it to multiple email addresses.
This PR will allow for setting multiple recipients as a comma separated string. In config mail.to.
e.g. 'to' => 'email1,email2...'
This is backwards compatible with the other way of passing an array with address and name. However, with multiple recipients it'll only support email addresses, since it'll become difficult to pass both name and address properly to SwiftMailer.

@RayDabbah please fix the StyleCI warnings.

Doesn't follow framework formatting conventions.


Allow mixed timezone and non-timezone coercion in timestamp column

Is your feature request related to a problem? Please describe.
Cannot coerce a pd.DataFrame column containing date strings with mixed timezone and no-timezones.
Describe the solution you'd like
A custom dtype that allows for mixed TZ and non-TZ date strings to be coerced into TZ-naive datetime (converting to UTC timezone)
Additional context
Example:
    schema = pa.DataFrameSchema({'TimeStamp': pa.Column(pa.dtypes.Timestamp, coerce = True)})
    df = pd.DataFrame(
        {'TimeStamp': ["2022-01-25T22:16:27.668Z", "10/28/2021 7:50"]}
        )

    schema.validate(df)

schema.validate will fail with pandera.errors.SchemaError: Error while coercing 'TimeStamp' to type datetime64[ns]: Could not coerce <class 'pandas.core.series.Series'> data_container into type datetime64[ns]. This is because there's one row with a TZ and one row without TZ.
We can fix this by adding a custom type that passes the utc = True parameter to pd.to_datetime.

thanks for posting this @ng-henry, would you mind creating a minimally reproducible example to help with debugging/iteration process?

pandera supports passing in kwargs to the pandas_engine.DateTime type so that you don't need to implement a custom type:
import pandas as pd
import pandera as pa
from pandera.engines import pandas_engine as pd_engine

schema = pa.DataFrameSchema({
    'TimeStamp': pa.Column(pd_engine.DateTime(tz="utc", to_datetime_kwargs={"utc": True}), coerce = True)
})
df = pd.DataFrame(
    {'TimeStamp': ["2022-01-25T22:16:27.668Z", "10/28/2021 7:50"]}
)

print(schema.validate(df))

The tz="utc" is to avoid the future warning:
FutureWarning: Using .astype to convert from timezone-aware dtype to timezone-naive dtype is deprecated and will raise in a future version.  Use obj.tz_localize(None) or obj.tz_convert('UTC').tz_localize(None) instead

We'll need to refactor the pandas_engine.DateTime.coerce method to follow the recommendation in the case that the user wants tz-naive datetimes.

Thanks! I didn't know how to construct that DateTime with custom args. That fixes the issue.


Question for sw-v7.0.0

I have seed 'Support method performance profile.' in sw-v7.0.0 CHANGELOGS,and I can't understand what that means.
Does it related to the whole link method level monitoring?
Or does sw-v7.0.0 support the whole link method level monitoring?
And how to made it or config it?
I need help

We have documentation for it, https://github.com/apache/skywalking/blob/master/docs/en/ui/README.md#profile
If you want to understand more, read

CN,  https://www.infoq.cn/article/CWUOl1JA0EyXw0CxQ4Zm
EN,  https://thenewstack.io/apache-skywalking-use-profiling-to-fix-the-blind-spot-of-distributed-tracing/

I recommend you to read all these.

We have documentation for it, https://github.com/apache/skywalking/blob/master/docs/en/ui/README.md#profile
If you want to understand more, read

CN,  https://www.infoq.cn/article/CWUOl1JA0EyXw0CxQ4Zm
EN,  https://thenewstack.io/apache-skywalking-use-profiling-to-fix-the-blind-spot-of-distributed-tracing/

I recommend you to read all these.

I got it,and it's help me a lot,thank you very much~


SafeHANDLE != operator should make parameters nullable

Describe the bug and how to reproduce
It's not a bug.

Expected behavior
No warning(CS8604).

Fixed in 4.0.1

The h1 seems also need to nullable. 😄

Corrected this and the == operator so null SafeHANDLEs are covered in 4.0.2


Is it possible to use hawck as screenkey

Can we create a script that render a black rectangle and the key pressed on top of it?
Any other enhancement (rectangle transparency, show several keys pressed) can be tackle later if this basic functionality is possible.
This tries to be a workaround for screenkey, which do not support wayland https://www.thregr.org/~wavexx/software/screenkey/#no-output-when-using-gnome-terminal-in-wayland

Yeah, that should be possible.
First enable unsafe mode by copying the __UNSAFE_MODE.csv file into /var/lib/hawck-input/keys, then write a script like this:
-- Note the lack of error-handling as this is only an example.
fifo_path = u.expandEnv("$XDG_RUNTIME_DIR/keys.fifo")
os.execute("mkfifo " .. u.shescape(fifo_path))
fifo = io.open(fifo_path)
-- NOTE: Be careful about using `any`, if the kbd:echo() isn't there
--       it will silence the keyboard
any => function ()
  fifo:write(kbd.event_code)
  fifo:write(" ")
  fifo:write(kbd.event_value)
  fifo:write(" ")
  fifo:write(kbd.event_type)
  fifo:write("\n")
  fifo:flush()
  kbd:echo()
end

Then have your display application listen on that fifo:
$ display-keys < "$XDG_RUNTIME_DIR/keys.fifo"

That's probably the easiest way to do this.

I tried to add the script with hawck-add but the command didn't end (as when I add the /etc/hawck/scripts/example.hwk) I tried to put a require "init" but nothing changes.

After put file in ~/.config/hawck/scripts it starts to work.
But io.open is a blocking operation, so I modify the script to show the keystrokes:
$ cat ~/.config/hawck/scripts/screenkey.hwk
any => function ()
  et = kbd.event_type
  if et == 0 then ets = 'UP'
  elseif et == 1 then ets = 'DOWN'
  elseif et == 2 then ets = 'REPEAT'
  end
  u.puts(kbd.event_code .. ', ' .. kbd.event_value .. ', ' .. ets)
  kbd:echo()
end

which outputs: (for a,s,d,f,F1,F2,F3,F4)
$ hawck-macrod --no-fork
"0, 0, UP"
"4, 30, UP"
"30, 1, DOWN"
"0, 0, UP"
a"4, 30, UP"
"30, 0, DOWN"
"0, 0, UP"
"4, 31, UP"
"31, 1, DOWN"
"0, 0, UP"
s"4, 31, UP"
"31, 0, DOWN"
"0, 0, UP"
"4, 32, UP"
"32, 1, DOWN"
"0, 0, UP"
d"4, 32, UP"
"32, 0, DOWN"
"0, 0, UP"
"4, 33, UP"
"33, 1, DOWN"
"0, 0, UP"
f"4, 33, UP"
"33, 0, DOWN"
"0, 0, UP"
"4, 59, UP"
"59, 1, DOWN"
"0, 0, UP"
^[OP"4, 59, UP"
"59, 0, DOWN"
"0, 0, UP"
"4, 60, UP"
"60, 1, DOWN"
"0, 0, UP"
^[OQ"4, 60, UP"
"60, 0, DOWN"
"0, 0, UP"
"4, 61, UP"
"61, 1, DOWN"
"0, 0, UP"
^[OR"4, 61, UP"
"61, 0, DOWN"
"0, 0, UP"
"4, 62, UP"
"62, 1, DOWN"
"0, 0, UP"
^[OS"4, 62, UP"
"62, 0, DOWN"
"0, 0, UP"
"4, 29, UP"
"29, 1, DOWN"
"0, 0, UP"
"4, 46, UP"
"46, 1, DOWN"
"0, 0, UP"
^C

I think I can read this output
$ display-keys <(hawck-macrod --no-fork)

but wonder if the fifo can be done in some way and a better parseable representation of a key

@albfan You can use require "json" for that, it has a serialization function:
local json = require "json"
local ss = json.sstream.new()
json.serialize(kbd, ss)
print(ss:get())

Nice, it looks basically as:
local json = require "json"
local ss = json.sstream.new()

any => function ()

  et = kbd.event_type
  ec = kbd.event_code
  ev = kbd.event_value

  key = {code = ec, type = et, value = ev }
  json.serialize(key, ss)
  print(ss:get())

  kbd:echo()
end

But is too low level. Not sure how to process combos etc, is there any doc for kbd? I think it has functions to report directly Ctrl+A etc

@albfan There are two ways to handle that.

Track the state of modifiers inside the display application, so inside the application responsible for drawing the key-presses you'll have something like this pseudocode:

if (code == ctrl) modifiers.ctrl.is_down = (val != KeyUp)
// Format
string out;
for (modifier : modifiers) {
  out.append(modifer.name + "+");
}
out.append(keyName(code));

Do it inside the script, hawck scripts already keep track of the state of modifier keys.

-- Untested, but you want something like this
function formatCurrentKey()
  local modifiers = {ctrl, alt, shift}
  local modifier_names = {"ctrl", "alt", "shift"}
  local out = ""
  for i, v in ipairs(modifiers) do
    if v() then
      out = out .. modifier_names[i] .. "+"
    end
  end
  return out .. kbd.map.keymap[code]
end

Got it. I will play around with that, thank!

FTR, maybe this could be added as another example
local json = require "json"
local ss = json.sstream.new()

any => function ()
  etype = kbd.event_type
  ecode = kbd.event_code
  evalue = kbd.event_value

  if etype == 1 then
    local m
    if evalue == 0 then
      m = "UP"
    elseif evalue == 1 then
      m = "DOWN"
    elseif evalue == 2 then
      m = "REPEAT"
    end

    key = {code = formatKey(ecode), mode = m }
    json.serialize(key, ss)
    print(ss:get())
  else
    key = {code = ecode, value = evalue, type = etype }
    json.serialize(key, ss)
    print(ss:get())
  end

  kbd:echo()
end

function formatKey(code)
  local modifiers = {ctrl, alt, shift}
  local modifier_names = {"ctrl", "alt", "shift"}
  local out = ""
  for i, v in ipairs(modifiers) do
    if v() then
      out = out .. modifier_names[i] .. "+"
    end
  end
  return out .. kbd.map.keymap[code]
end

which output (a,Ctrl+a):
{
  "code": "a",
  "mode": "UP"
}
{
  "code": "a",
  "mode": "UP"
}
{
  "code": "ctrl+a",
  "mode": "UP"
}
{
  "code": "ctrl+a",
  "mode": "DOWN"
}

I'm not sure about special keys (this is raw output from volume mute/up/down):
{
  "value": 160,
  "code": 4,
  "type": 4
}
{
  "value": 176,
  "code": 4,
  "type": 4
}
{
  "value": 174,
  "code": 4,
  "type": 4
}

@albfan I'm working on a scripts collection to distribute with the Hawck installation, and I'll definitely add the key-press printer as an example.
I can't do it right now however, as there is a blocking feature needed, called passthrough-scripts. Once passthrough-scripts are implemented, I can add the printer script to the collection.

Cool!. Just let me know and I will improve when I identify more special keys. Example:
vol keys for screenkey:

https://gitlab.com/screenkey/screenkey/-/blob/master/Screenkey/labelmanager.py#L80
https://gitlab.com/screenkey/screenkey/-/blob/master/Screenkey/labelmanager.py#L84
https://gitlab.com/screenkey/screenkey/-/blob/master/Screenkey/labelmanager.py#L86

etc...


cool!

this looks like a very interesting project! what is the progress, and any more docs behind its design?
keep it up, cheers.

progress: The Loader module is implemented and tested for 64-bit ELF, PE32+, and Mach-O files. The rest of the Microcode abstraction layer (MAL) is implemented for x86_64+Linux and tested on few C programs linked with the standard C library. However, not all x86_64 instructions are supported yet. Currently we (i.e. the project leader Emmanuel Fleury (see the user perror) and me) are working on the first CFG-recovery analysis based on the test input generation (see 'analysis/native_execution').
docs: There is a 53 pages long LaTeX document 'doc/CFG_recovery/CFG_recovery.tex' accurately describing design of all key components of the project. We plan to add another document related to the analysis we are working on. We also plan to add more Doxygen comments into the code.


copyright year updated to 2022

In footer section the copyright year is updated from 2021 to 2022
In Example section "/" is added for closing  tag

I have updated the copyright year 2022 and added a close tag for  in Examples section
you can merge this !

its invalid because there is no issue for it


Field name is not working because the new vizjson structure

STEPS

Paste viz.json url.
Select layer in Layer name.
The tool does not return any field on the Field name.

This can be due to the changes in the new viz.json structure.
cc @AbelVM

Fixed in v. 0.23


CalendarLayout listener for status expanded/shrinked

Hey,
Is there a way to listen for changes between the status/state of the CalendarLayout? Something like CalendarLayout.onChange(isExpanded: Boolean)?
Thanks!

I'am looking for that listener is it already implemented ?

@curiousily

@curiousily @tjouin I am also looking for same. Is it available?


add Czech and Slovak mapping for MacBook Air

OS X version: El Capitan
Karabiner version: 10.22.0
Your Mac hardware: MacBook Air 13, Early 2015
Your keyboard hardware: MacBook Air keyboard

I made derivate of czech.xml. The original czech.xml is based on CONTROL_R which is not available on MacBook Air. I changed the CONTROL_R to Option_R. The Option_R is common mapping also on Windows. The new file has name czech_macbook_air.xml.
Then I made copy of this file and stored it under slovak.xml. While Czech and Slovak are very close there are some differences and I recommend to keep the file separate for corrections of mapping in future.
Please review the suggested change. I'll be happy for any feedback. Thank you.

Thanks!


React-router with Express server: GET request does not work properly.

Version
4.1.1
Express: 4.14.1
http-proxy-middleware:  0.17.3
Test Case
I am using an Express server to mock my REST calls. (also tried with other solution)
Once I add the react-router to handle the navigation, all the GET request return the index.html instead of the mock data.
For example:
<Switch>
<Route exact path='/' component={LoginPage}/>
<Route exact path='/login' component={LoginPage}/>
</Switch>
Steps to reproduce
call GET /localhost:3000/login/authentication
Expected Behavior
Response status 200, body with token
Actual Behavior
I get in the response the index.html file.
Moreover, if in the path I add v1.0
For example: GET /localhost:3000/v1.0/login/authentication, it will work.

It's not made to handle routing for express, it's made to use with react.

I use React of course, express is used only as a server, and in my case, only to mock the REST calls.

Please ask usage questions on StackOverflow/Reactiflux. The issues section here is (mostly) for bugs.
If you open a question on StackOverflow, I would recommend including the actual code from your server. What you have included above does not provide nearly enough information for someone to help you.
I will say that if you're just handling routing in Express and not doing server side rendering, then all of your routes should just be returning index.html and the client side should be handling the rendering. Once again, that is something that seeing the actual server code should clear up.

Ok thank you for your help.


Removal of the Santa Hat and kowtowing to SJWs

The removal of the santa hat, and kowtowing to a single SJW, is incredibly offensive to me. Please rectify this as soon as possible.

Without a hat the settings icon may get cold

duplicate of #87291

Thanks for creating this issue. We think this issue is unactionable or unrelated to the goals of this project. Please follow our issue reporting guidelines.
Happy Coding!


Feedback for Motorola page

I have spoken several times with Verizon assistants, with technical support, also with technical support of Motorola as well that have relayed that the Moto G Power 5G I have is State-of-the-art with Android 14 Software.  It has BT 5.3 as well which is the highest on market. It has everything it absolutely needs to fit criteria.  With wifi I had a technician over while my watch was going off.
His monitoring system read no defaults in action with my internet.  That was with my Samsung AO3s. For my Motorola though I can turn my data off and run it directly from my wifi. Nothing else in my house is having faults. Nothing else I am connected to is either, absolutely nothing.
I had several indepth conversations with high-end technicians and professionals with Verizon and Motorola that say it is 100% that Empatica is not keeping up with updates on others sides to which there are mishaps of their responsibility.  They've rest assured and promised me several times now.

There is no "advanced" setting on the Moto G Power 5G as the technician and I hadn't been able to find. We did establish the principles though easily as they were already set in mind for this app.


Why does /convert-token require client_id and client_secret if you're sending Authorization header

We have a way user's can connect multiple accounts once authenticated, but the library still requires we send the client_id and client_secret for /convert-token even though we've setup the Authorization Bearer token by this point.

You need your client id for django to identify which Application the token should be attached to.
Basically, everytime you are generating a new token, an application id will be needed.

You have the Bearer, it can be inferred from that without further exposing
the client secret? No?
On Fri, Jul 21, 2017, 7:24 AM Philip Garnero<EMAIL_ADDRESS>wrote:

You need your client id for django to identify which Application the token
should be attached to.
Basically, everytime you are generating a new token, an application id
will be needed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PhilipGarnero/django-rest-framework-social-oauth2/issues/108#issuecomment-316987357,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACTyQNyjoLhg9CR2pgZ9dR8Ppr4Bvomks5sQJhfgaJpZM4OeY3M
.

--
Thank you,
Josh Turmel
Future Haus

This is not part of the oauth2 protocol but yes it is possible.
If you want to implement it yourself, you could take a look here and subclass ConvertTokenView to retrieve the client_id from the token in your header.


Release v3.5.0

Changes since v3.4.0

Use correct kubeconfig context on terminal when switching cluster (#461)
Track telemetry pref changed event (#445)
Enable win integration tests (#424)
Fix icon.ico (#440)
Improve Helm release version detection (#422)
Fix error when closing Lens on Windows (#413)
New logo (#423)
Bump websocket-extensions from 0.1.3 to 0.1.4 (#409)
Bump websocket-extensions from 0.1.3 to 0.1.4 in /dashboard (#408)
Remove Helm release update checker (#420)
Integration tests using spectron (#410)
Fix app freeze after closing terminal on Windows (#411)
Add download-bins target to make (#406)
Add arch node selector for hybrid clusters (#400)
Dynamic dashboard UI based on RBAC rules (#366)
Show owner reference on all resource details (#399)
Fix pod shell command on Windows (#402)
typo/translation correction: transit to transmit (#359)
Fix @babel/preset-env version (#401)
Unify scrollbars/paddings across supported OS (#367)
Remove Kontena reference from Lens logo (#357)
Replace admin check with check for access (#297)

@nevalla PTAL