Tell me how much does it cost to chat 500 tokens

good afternoon

Hello, I am your assistant on GitHub, built by the Second State team. I assume you are referring to a chat service or a messaging service that uses tokens as a form of payment. The cost of 500 tokens would depend on the service provider and the cost per token they have set. You would need to check with the service provider to determine the cost of 500 tokens.

It's really painful to work with this function.

It's very very bad


Rename Assembly in Compliance to RFC 0004-Adapter-Extensibility

Renames the BoostTestAdapter.dll assembly to BoostTestAdapter.TestAdapter.dll in accordance to RFC 0004-Adapter-Extensibility. This allows clients to run the adapter through vstest.console.exe using the /testadapterpath: command-line argument without needing to install the adapter via the VSIX installer.
In addition, the repository configuration is updated to avoid huge line-diff changes.

@netspiri there is a merge conflict. Please rebase and upload again.

Fixed


Request: Allow syncing core plugin settings and editor settings

Hi! First of all, thank you so much for making this plugin, I am absolutely loving it so far.
However, now that you can sync plugins and their settings, I was wondering if there was also the possibility of adding the following features:

The ability to sync core plugins and their settings
The ability to sync editor settings, like app.json, appearance.json and so on.

These features would be very useful to me, and I'm sure they would also benefit other users. Thanks!

Thank you for using this plugin! I'm very honored!
If you don’t want real-time detection (as same as plugin sync), it's not so difficult.
But I don't sure that obsidian detects the modification of these files.
I'll try and test once!

Progress report!!
First of all, It will be implemented with some limitations!
The limitation is based on simple reasons, Obsidian doesn't notify changes about these files.
So we have to check the file status as periodical (in livesync) or before replication at once(in a periodical or manually sync).
Therefore, conflict resolution is required, but the content difference wouldn't help us. We have to keep the clock synchronized more than before. (But it's the same condition as other synchronizing solutions, it will be not so fatal.). the latest file will be a winner.
So, we have to choose what we sync or not sync. It will be as regular expressions.
Plugin folders will be synchronized too. But I will not implement that reloading plugin automatically. It made serious trouble in developing.
In a few days or a week, this feature will be released as an experimental feature.

Hi! I finally got around to testing this feature.
While it works great with plugins and their settings, it doesn't appear to work as expected with Obsidian's default settings. When reloading after the settings are synchronized, it appears that Obsidian saves its settings to the files anyway, overwriting the synchronized settings.
Not only does this cause Obsidian to ignore the synced settings, but it also causes LiveSync to now think that the settings have changed (due to Obsidian overwriting them), causing Obsidian's default settings to be uploaded as the "changed" settings.
It seems like you have to find some way to force Obsidian to reload without causing it to save its settings to the settings files first.

Thank you for checking this plug-in!
Wow, has overwriting processed after synchronisation? Or while in synchronisation?
And could you please check the behaviour when you rewrite them by older revision again by "pick a file to show history"?
If it works, the workaround will be found soon.

It seems like you have to find some way to force Obsidian to reload without causing it to save its settings to the settings files first.

Yes, you right. I thought I found that and implemented but seems it is not enough for some environment.
May I ask your environment?
You can copy that by Ctrl + P -> Show debug info

Hi! As I said, the overwriting seems to happen right before Obsidian reloads when pressing the reload link in your notification. What seems to happen is that Obsidian saves its currently applied settings into the settings files before reloading, which causes all of the synchronized settings to be overwritten.
My environment is this:
SYSTEM INFO:
	Obsidian version: v0.15.9
	Installer version: v0.14.15
	Operating system: Windows 10 Pro 10.0.22000
	Login status: logged in
	Catalyst license: insider
	Insider build toggle: on
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: Atom
	Snippets enabled: 3
	Restricted mode: off
	Plugins installed: 19
	Plugins enabled: 19
		1: Kanban v1.3.15
		2: Icon Folder v1.3.31
		3: Calendar v1.5.10
		4: Dataview v0.5.41
		5: Kindle Highlights v1.6.3
		6: Paste URL into selection v1.7.0
		7: LanguageTool Integration v0.3.0
		8: Export To TeX v0.4.2
		9: File Explorer Note Count v1.2.0
		10: Custom Frames v2.4.2
		11: Periodic Notes v0.0.17
		12: Natural Language Dates v0.6.1
		13: Pandoc Plugin v0.2.5
		14: Recent Files v1.3.3
		15: Remember File State v1.0.6
		16: Regex Find/Replace v1.2.0
		17: Completr v2.9.0
		18: Focus Mode v1.9.0
		19: Commander v0.1.0

Hi! Any update on this?

I apologise for the lack of posts.
In fact, I missed it when focusing on other issues, trying to make sure the conditions to reproduce it. So sorry.
At the moment I haven't found a way to intervene in the writing and reading of Obsidian settings.
However, it seems that the method of saving files has changed a bit recently. I will have to investigate this a bit more.

I also fogot to notify you of this.
Even if we lost some configuration by something, we can retreive it again by Pick a file to show history, choosing json file and old revisions, and pressing Back to this revision.
In most cases, this should help us.
It may be better to check for differences and merge them, rather than simply applying a new file to a particular file.
(However, this requires knowledge on a each file.)
Could you please check the differences by this feature and let me know when some configuration has been gone?

Sync of obsidian settings and core plugins with settings would be great.
Let me know if you need help with testing anything.

I completely forgot why this issue is not updated (Sorry...). I should have posted the progress.
However hidden files can be synchronised, and changes are automatically detected now.
@OvrAp3x
Could you please enable Sync hidden files and check the behaviour? I would like to close this issue if it looks good.

I tested with that on previously without success, however today I tried to run the "touch hidden files" and again tried tonsetup a new device. This time it worked.
Obsidian specific settings was synced.
The "only" issue I found is that synced plugins are no enabled by default, but seems it has to be done manually.
But settings for those are kept, so not a big deal.
Great work, love the plugin😊

Hi @vrtmrz, do you know if this has been fully fixed? Unfortuantely I haven't been able to test it again yet, but I'd love to get back to the plugin if this feature is fully completed now.

Yes, I think so. Hidden files are now synchronised correctly, and if there are conflicted changes, this plug-in merges their changes into one setting (Where there has been no essential conflict, such as editing the same item)
Therefore, now we have fewer possibilities of overwriting that for resolving conflicts.

That's great to hear, thank you so much!!
Also, just to confirm: When I enable the "sync hidden files" option, all files in the .obsidian directory are synchronized, correct? That means that additionally using the "sync plugins" option (where you can select individual plugins and their settings) isn't necessary, and wouldn't produce the intended result since all plugins are synced anyway, correct?

 Thank you for contributing to making the plugin better too.
Yes, all files under the dir .obsidian are fully synchronised. But  Skip files can be configured for Hidden files sync.These plug-ins are still able to be handled by plugin-sync.
You can use both methods at once, for them.
(I configure it to ignore several plug-in directories on hidden files sync, but plugin-sync scans them;  to make be able to roll it back.

Hi! I finally got around to testing this feature.
While it works great with plugins and their settings, it doesn't appear to work as expected with Obsidian's editor settings. When reloading after the settings are synchronized, it appears that Obsidian saves its settings to the files anyway, overwriting the synchronized settings.
Not only does this cause Obsidian to ignore the synced settings, but it also causes LiveSync to now think that the settings have changed (due to Obsidian overwriting them), causing Obsidian's default settings to be uploaded as the "changed" settings.
It seems like you have to find some way to force Obsidian to reload without causing it to save its settings to the settings files first.
(Obsidian's default Sync plugin also has the option to sync settings like this, so maybe you can try to figure out how that plugin does it? Not sure, but good luck!)

Hmm, it seems like I'm still getting this issue with the most recent version of the plugin. Files like appearance.json, app.json, core-plugins.json, community-plugins.json and more seem to be force-saved by Obsidian after this plugin has already downloaded and written them to disk. This occurs even if I press the "restart" link in the popup that this plugin displays when hidden files changed.
The only way to fix this issue is to manually go into the "Select a file to show history" view, going back to the previous version, and then immediately using the "Restart without save" command in Obsidian to reload the app. This is quite tedious, unfortunately.

Finally reproduced and understood, I really appreciate your patience and explanation. And absolutely quite tedious to fix overwritten files.
I added some internal-method calls, To notify Obsidian of changes to hidden files. We are not sure if it is correct due to the internal API, but I hope that this makes the issue better.
I always appreciate your efforts in helping with tests, would you kindly assist by trying 0.17.20 too?

I just tried a fresh install of the plugin and database with 0.17.20, and the exact same issue still seems to be happening. I recorded this video to show the changes in appearance.json: When the file is downloaded, the correct version is created (first revision), but then when Obsidian either exits or opens after pressing the "Restart" button in your popup, it reverts to the default appearance settings.
https://user-images.githubusercontent.com/5741138/215466402-a948e5b8-7e5c-437b-89b5-b3e8ea981dac.mp4

Oh, sorry to let you disappointed! thank you for your fast review and screen recording.
It appears to be as you say. May I ask about the platform?
Also, it would be nice to have the logs that include three writings until it is overwritten again, with the Verbose log enabled.

Thank you very much! These logs helped us!
When the conflict has been detected, the plugin will be trying to find the revisions which have been commonly used. If found,  merge each difference from that one and apply. If not,  simply overwrite with a newer one.
Files on new devices have no older revision. And of course, they are new.
Therefore, our config files have been overwritten, unfortunately.
We have to address first-rev items.
This is the intermediate report! Thank you for your kindness!

@Ellpeck Thank you for your patience! Now, we are able to check the difference between them, and choose one of them or merge them!
Could you please check v0.17.21?

Sorry that it took me so long to test this, but it seems that LiveSync now asks you which version of some files (appearance, community plugins and core plugins) you want to use, and restarting after selecting the desired one does indeed restore that configuration!
In my specific test, it synced the appearance and app settings files without me having to resolve any issues, and the files named above with some help, however, the hotkeys file was not flagged as a conflicting file and the default hotkeys ended up overwriting the custom ones i had set. For some reason, the second device's revision list for the hotkeys file only has a single revision (the empty one), while I already reverted to a previous revision on the original device. The hotkeys file was then extremely stubborn, only finally synchronizing to the second device after using the "Sync hidden files" option as well as syncing again multiple times.
Overall, the hotkeys thing is the only real issue I'm having with the hidden file syncing now, which is great progress!

Thank you for your testing! I am very pleased to hear that it works almost well.
Such behaviour was not expected. Not necessarily because of this, but when using fetch, 'hidden file sync', 'plugins and...' are now temporarily disabled since the v0.17.29.
I hope that it makes the situation easier.


About creating my own data set

I want to add my own dataset based on the 3DMatch dataset. How do I create it? In 3DMatch data file, the training set and the test set are both a.txt file and a.pth file. What is the matrix in the.txt file? I also want to know where to store the conversion matrix between source point cloud and target point cloud (for point cloud registration training)?

I want to add my own dataset based on the 3DMatch dataset. How do I create it? In 3DMatch data file, the training set and the test set are both a.txt file and a.pth file. What is the matrix in the.txt file? I also want to know where to store the conversion matrix between source point cloud and target point cloud (for point cloud registration training)?

Could you please  successfuly create your  own dataset based on the 3DMatch dataset?


#284 Missing AMD definition fix in the 01-into.js.

This is a missing piece of the fix for #284. 01-intro.js should also be fixed otherwise this AMD definition will still be incorrect upon the project build (grunt concat task).

Is this PR still relevant?


Correctly initialize the block type controllers from the BlockType entity

This really should be centralized to something like a factory. All these required changes shows how decentralized and scattered this stuff is. :+1:


ReducerProject - TS side

This is still messy and I don't think this should be merged before the cleanup.
Pushing to share the code so far.
Stuff that works:

no typescript compilation errors
components (e.g. playground) render basic values, distributions and records
most internal Rescript values are wrapped as Typescript classes

Stuff that's broken:

[x] functions don't render at all; <FunctionChart*> components are commented out entirely, because runForeign is dead, and I haven't implemented the new approach with code generation yet
[ ] <SquigglePartial> is broken, frontend components are not making use of the new Project APIs and are unable to wire up multiple sources together

Note: <SquigglePartial> is salvageable with new approach and props changes, but <SquiggleEditorWithImportedBindings> is probably not

[x] bindings don't render; to render multiple values, return records in the last statement
[x] TS tests in squiggle-lang
[ ] jsImports don't work

Internal stuff that needs to be cleaned up:

[x] most of the old code in squiggle-lang/js/ is commented out and not deleted, for my own reference during the transition
[x] need to rename TS wrapper classes with Sq prefix
[x] need to change enums to string values and clean up names (type-signifying prefixes are unnecessary)

"" <- We can/should probably drop that component, given that we are dropping bindings

Small notes, from a quick read:

Nice work! Overall looks fairly strong.
Right now we just really need the minimal amount of code for step #2 here: https://docs.google.com/document/d/1Yu0PW-WIK09hVx_1XVeb6BOVNvqIiDZl7yR6kq9-xcQ/edit. I'm not sure if we need SquigglePartial or some of the bindings stuff. We also don't really need many of the Distribution functions.
Keep PRs small-ish. File stories for new things to improve, outside of the minimum necessary for #2.

because runForeign is dead, and I haven't implemented the new approach with code generation yet

Maybe we could push a version without this working, then have a new story to implement it. Do feel free to communicate with @umuro on exactly how this could be done.

@berekuk I am Ok with your ReScript changes

bindings don't render; to render multiple values, return records in the last statement

Any chance we could soon get bindings to render? This was nice, before.

Going over this again, I don't see anything that's really objectionable. I'm not sure about some of the tradeoffs we're taking (in that I imagine there must be a few, but don't fully understand them), but happy to go with this strategy now.

Not sure where this is caused, but:
https://github.com/quantified-uncertainty/squiggle/issues/1013

Tiny point, but can you change "System.version" from "0.3.0" to "0.4.0-dev" or similar, with this PR?

Tiny point, but can you change "System.version" from "0.3.0" to "0.4.0-dev" or similar, with this PR?
Done.

Rant on type safety.
Unrelated to any decisions, but I'd like to make this common knowledge.
Turns out it's really easy to write code that's type safe in letter but not in spirit. Our current approach with wrapper TS classes makes me painfully aware of that. What we're doing is still needs to be done, but type safety currently doesn't help at all, it just creates the fake sense of safety. Beware.
Example:
export class SqSampleSetDistribution extends SqAbstractDistribution {
  tag = Tag.SampleSet;

  value() {
    return valueMethod(this, RSDistribution.getSampleSet);
  }
}

export class SqSymbolicDistribution extends SqAbstractDistribution {
  tag = Tag.Symbolic;

  value() {
    return valueMethod(this, RSDistribution.getSymbolic);
  }
}

If I made a typo and switched the tag values, nothing would complain. If I mixed up RSDistribution functions, also nothing would complain. If I made a typo in the class name, nothing would complain.
Same with tagToClass dicts:
const tagToClass = {
  [Tag.PointSet]: SqPointSetDistribution,
  [Tag.SampleSet]: SqSampleSetDistribution,
  [Tag.Symbolic]: SqSymbolicDistribution,
} as const;

There are also cases like this on Rescript side. Every time we create an additional abstraction layer like this for proxying calls, we don't just make extra tedious keystrokes, we also increase the probability of typos.

Got the tests to pass, and opted to add a value method to the Void value to make the tests easier
I skipped two tests fast-check as they are failing due to having difficulty formatting extremely small numbers. There used to be a feature where you could create a Sample Set distribution directly through JS without executing Squiggle. That feature has now gone (as genericDist is now opaque) so removed them until that feature comes back (which probably won't be in a while, seems very low priority)

Got the tests to pass, and opted to add a value method to the Void value to make the tests easier

Thanks!
Note that there's still:

a big portion of __tests__/TS/JS_test.ts that is commented out and needs to be reimplemented
a note in testRun implementation about missing environment (and since imports and bindings got removed, you'll need to figure out how to rewrite tests without them; both should be replaced with multi-source projects)

#1029 is fixed with latest commits: https://deploy-preview-1011--squiggle-documentation.netlify.app/playground/#code=eNpFi70OwiAURl%2BF3KlVFjuSOPoEjNIBFfAmcBv5iZiGdxdtjGc630m%2BFdJ9ecoSgo4vEFb7ZPi3nW6Ylwgix9ILEmbUXj4KOueNzBHJgQA71JEdGS0xaD%2FU%2FYFPoyK31bqbFEWTuq6KWEeLn324CGb5f14FO%2Fc%2Fd%2FPWmqIG7Q1BbzFp
I'm almost ready to merge this now and continue working on other features (e.g. jsImports) in other PRs.
But there's an issue with Parser_test.ts, which is currently broken, because new SqValue instances are not comparable with expect(x).toEqual(y) anymore.

Oh, and there's also a big issue with rendering lambdas that come from end expressions. That's not possible and won't ever be possible. We're still figuring the consequences of that with Umur in https://eaforecasting.slack.com/archives/C030T49UHSS/p1661855297115039.

(I added epic-reducer-project to ci branches in develop, so if you git fetch && git merge origin/develop jobs should trigger)

I'm going to merge this.
Most of TS tests are fixed (I left some commented ones for old distributions methods).
Lambdas still don't render in end expressions, but I'll fix that after Umur implements implicit __result__ binding.
Viewer is now back to "either result or bindings if result is empty" pattern, same as it worked in 0.3.


Webservice Files for JBrowse (workflow)

workflow steps related to making webserivce files for jbrowse
annotated proteins fasta / fai
jbrowse conf

Data loaders should coordinate these changes with ones needed for pseudogene bug / b68.  (although pseudogene / download files will only affect a small number of genomes while this change requires running for all genomes)

approved by data loaders together


Clarify that using printf formatting is for security

See https://github.com/OCA/pylint-odoo/issues/302.

FYI @moylop260

@sbidoul @gurneyalex
Could you give me permissions to merge in this project, please?

Could you give me permissions to merge in this project, please?

Hi @moylop260 currently only board has access to this repo, probably because it is (was?) the OCA website.
We can open the discussion on who should be added, but in the meantime, just @ mention me and I'll review and merge.


Bug: Applying filters to tasks.list doesn't work

label-studio-sdk version: 1.0.5, label studio version: 1.13.1 (Docker deployment)
When i try to apply a filter it always returns all the tasks not just the one i'm filtering for and no error is received
filters = Filters.create(Filters.AND, [Filters.item(Column.inner_id, Operator.EQUAL, Type.Number, Filters.value(1))])
task = ls.tasks.list(project=project_id, query={"filters": filters})
Please let me know if you need more information.

You need to supply a str for the query parameter. It should be query=json.dumps({"filters": filters}).

Hello,
I've got the same problem, @MmAaXx500 comment made is possible to fix this on my side. Maybe some example in the Docs might be useful.

@MmAaXx500 thank you very much :)

@MmAaXx500 Thank you!


CORS issue if jot-server is installed on another server.

CORS issue is occurring if jot-server is installed on another server and UNA app on another server. Also in documentation there is no detail if we use other server for jot-server.

Jot Server can be installed on another server and one Jot Server instance can be used for many different domains simultaneously.
You may see CORS problem in browser console in case if Jot Server was installed on the server with not valid certificate or in Jot Server's config was defined wrong paths to certificate files. Also when port on the server with Jot Server is closed for external connections.
Check please if the port with running Jot Server is available for connect with command:
telnet yourdomainname.com port

Jot Server can be installed on another server and one Jot Server instance can be used for many different domains simultaneously.
You may see CORS problem in browser console in case if Jot Server was installed on the server with not valid certificate or in Jot Server's config was defined wrong paths to certificate files. Also when port on the server with Jot Server is closed for external connections.
Check please if the port with running Jot Server is available for connect with command:
telnet yourdomainname.com port

Ok,  Thank you for information :)

Ok,  Thank you for information :)


Dropping video frames results in frozen video stream

Hi,
thanks a lot for the good work! I am playing around with your test example, and I am facing a pretty weird bug/problem.
Essentially, in a very unreliable way, the video stream from the drone suddenly freezes, causing opencv to always show the very last frame grabbed. I have placed few debugging output here and there, and I have found out that when the freeze happens, in the method
ARDrone::getVideo
the statement
av_read_frame(pFormatCtx, &packet)
is never >= 0, hence no packets are parsed and the loop in
ARDrone::loopVideo
breaks.
I am not sure what could be the problem. I am on Ubuntu 14.04, Ar.Drone Ver. 2.4.8. Have you ever faced this problem? I have tried to change sleeping times (increasing/decreasing them), with no luck. Also, this is completely random. Sometimes I am able to fly and show video without any problem, but most of the time I can only show the video for few seconds. All other communication work fine. Another interesting behavior is that the program has about 5--8 seconds hanging time between when the Drone version is printed and when the first frame comes in (or at least is shown by opencv).
Thanks a lot for your help!
-Fabrizio

Nothing happened ?


build: validate commit messages

Prevent contributors from commiting unconventional messages
by having husky execute commitlint
https://commitlint.js.org/
Co-authored-by: Marc Mintel<EMAIL_ADDRESS>

@all-contributor please add @mmintel for build

@all-contributors please add @mmintel for build

🙄
@all-contributors please add @mmintel for infra


Popup documentation page is broken

Steps

Load Popup docs page.

Expected Result
It should load with all the documentation and examples.
Actual Result
It loads the header and props but not the examples.
If it's a fresh load directly to http://react.semantic-ui.com/modules/popup then it's just a gray screen.
Here is the error in the console:
Uncaught Error: Cannot find module './modules/Popup/Types/PopupExample.js'.
    at app.e58e193a1f06c9b1affd.js:4169
    at o (app.e58e193a1f06c9b1affd.js:4169)
    at a (app.e58e193a1f06c9b1affd.js:4169)
    at ComponentExample._this.renderOriginalExample (app.e58e193a1f06c9b1affd.js:14)
    at ComponentExample.value (app.e58e193a1f06c9b1affd.js:14)
    at performInitialMount (react-dom.min.js:13)
    at p.mountComponent (react-dom.min.js:13)
    at Object.mountComponent (react-dom.min.js:14)
    at h.mountChildren (react-dom.min.js:14)
    at h._createInitialChildren (react-dom.min.js:13)

react-dom.min.js:13 Uncaught TypeError: Cannot read property '_currentElement' of null
    at p._updateRenderedComponent (react-dom.min.js:13)
    at p._performComponentUpdate (react-dom.min.js:13)
    at p.updateComponent (react-dom.min.js:13)
    at p.receiveComponent (react-dom.min.js:13)
    at Object.receiveComponent (react-dom.min.js:14)
    at Object.updateChildren (react-dom.min.js:13)
    at h._reconcilerUpdateChildren (react-dom.min.js:14)
    at h._updateChildren (react-dom.min.js:14)
    at h.updateChildren (react-dom.min.js:14)
    at h._updateDOMChildren (react-dom.min.js:13)
    at h.updateComponent (react-dom.min.js:13)
    at h.receiveComponent (react-dom.min.js:13)

I'm still able to switch to Popup.Content and Popup.Header but I can't go to another page. It'll change the address URL but nothing happens.
Version
Current live version (0.62.3)
Testcase
http://react.semantic-ui.com/modules/popup

Thanks, fixing going out soon.  See #1056.


Help Me: My Telegram account has been logout on my device

My Telegram account has been logged out on all devices, and I no longer have access to the phone number to request OTP. However, I checked on my VPS, and it turns out that my Telegram session in Selenium is still running and has not been logged out. To ensure that the session is still active, I tried running one of the Telegram games like ./launch.sh seed and logged in using the Telegram session that I had previously backed up when I first ran the script. Now, the question is, how can I log in again to my Telegram app on my device?

Hi,
You can create a Python file to extract the OTP. Here's how:

On your VPS, save the script at the bottom of this reply in your games folder as otp.py:

Run the script on your VPS using this command:
./launch.sh otp

When prompted, select No to updating the settings.

Choose any wallet name or use the default.

Attempt to log into your Telegram account on your preferred device via the phone number and OTP method.

Once the OTP has been sent, go back to your VPS, and select the account from your saved Telegram session.

The VPS will return a message like The most recent OTP was: 12345...

Enter the OTP on your preferred device, and you should be logged back into your Telegram account.

import os
import shutil
import sys
import time
import re
import json
import getpass
import random
import subprocess
from PIL import Image
from pyzbar.pyzbar import decode
import qrcode_terminal
import fcntl
from fcntl import flock, LOCK_EX, LOCK_UN, LOCK_NB
from selenium import webdriver
from selenium.webdriver import ActionChains
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.chrome.service import Service
from selenium.webdriver.chrome.options import Options
from selenium.webdriver.common.keys import Keys
from selenium.common.exceptions import NoSuchElementException, TimeoutException, StaleElementReferenceException, ElementClickInterceptedException
from datetime import datetime, timedelta
from selenium.webdriver.chrome.service import Service as ChromeService

from claimer import Claimer

class OTPFinder(Claimer):

    def initialize_settings(self):
        super().initialize_settings()
        self.script = "games/cold.py"
        self.prefix = "BNB-Cold:"
        self.url = "https://web.telegram.org/k/#777000"
        self.pot_full = "Filled"
        self.pot_filling = "Mining"
        self.seed_phrase = None
        self.forceLocalProxy = False
        self.forceRequestUserAgent = False
        self.start_app_xpath = "//button//span[contains(text(), 'Open Wallet')]"

    def __init__(self):
        self.settings_file = "variables.txt"
        self.status_file_path = "status.txt"
        self.wallet_id = ""
        self.load_settings()
        self.random_offset = random.randint(self.settings['lowestClaimOffset'], self.settings['highestClaimOffset'])
        super().__init__()

    def next_steps(self):
        # Initialise Chrome/Chromium & load the login notification service user (ID 777000)
        self.step = "01"
        self.driver = self.get_driver()
        self.driver.get(self.url)
        # Check for the last OTP & Print it
        xpath = "(//span[@class='translatable-message'])[last()]"
        self.target_element = self.move_and_click(xpath,10, False, "read the last OTP code ", "08", "visible")
        OTP = self.monitor_element(xpath, 10, "grab the last OTP")
        OTP = self.strip_html_and_non_numeric(OTP)
        print(f"The most recent OTP was: {OTP}")
        # Close the session
        self.quit_driver()

def main():
    claimer = OTPFinder()
    claimer.run()

if __name__ == "__main__":
    main()

Hi,
You can create a Python file to extract the OTP. Here's how:

On your VPS, save the script at the bottom of this reply in your games folder as otp.py:
Run the script on your VPS using this command:./launch.sh otp

When prompted, select No to updating the settings.
Choose any wallet name or use the default.
Attempt to log into your Telegram account on your preferred device via the phone number and OTP method.
Once the OTP has been sent, go back to your VPS, and select the account from your saved Telegram session.
The VPS will return a message like The most recent OTP was: 12345...
Enter the OTP on your preferred device, and you should be logged back into your Telegram account.

import os
import shutil
import sys
import time
import re
import json
import getpass
import random
import subprocess
from PIL import Image
from pyzbar.pyzbar import decode
import qrcode_terminal
import fcntl
from fcntl import flock, LOCK_EX, LOCK_UN, LOCK_NB
from selenium import webdriver
from selenium.webdriver import ActionChains
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
from selenium.webdriver.chrome.service import Service
from selenium.webdriver.chrome.options import Options
from selenium.webdriver.common.keys import Keys
from selenium.common.exceptions import NoSuchElementException, TimeoutException, StaleElementReferenceException, ElementClickInterceptedException
from datetime import datetime, timedelta
from selenium.webdriver.chrome.service import Service as ChromeService

from claimer import Claimer

class OTPFinder(Claimer):

    def initialize_settings(self):
        super().initialize_settings()
        self.script = "games/cold.py"
        self.prefix = "BNB-Cold:"
        self.url = "https://web.telegram.org/k/#777000"
        self.pot_full = "Filled"
        self.pot_filling = "Mining"
        self.seed_phrase = None
        self.forceLocalProxy = False
        self.forceRequestUserAgent = False
        self.start_app_xpath = "//button//span[contains(text(), 'Open Wallet')]"

    def __init__(self):
        self.settings_file = "variables.txt"
        self.status_file_path = "status.txt"
        self.wallet_id = ""
        self.load_settings()
        self.random_offset = random.randint(self.settings['lowestClaimOffset'], self.settings['highestClaimOffset'])
        super().__init__()

    def next_steps(self):
        # Initialise Chrome/Chromium & load the login notification service user (ID 777000)
        self.step = "01"
        self.driver = self.get_driver()
        self.driver.get(self.url)
        # Check for the last OTP & Print it
        xpath = "(//span[@class='translatable-message'])[last()]"
        self.target_element = self.move_and_click(xpath,10, False, "read the last OTP code ", "08", "visible")
        OTP = self.monitor_element(xpath, 10, "grab the last OTP")
        OTP = self.strip_html_and_non_numeric(OTP)
        print(f"The most recent OTP was: {OTP}")
        # Close the session
        self.quit_driver()

def main():
    claimer = OTPFinder()
    claimer.run()

if __name__ == "__main__":
    main()

showing error like this

i check the logs error showing like this
Traceback (most recent call last):
File "/root/HotWalletBot/games/seed.py", line 268, in
main()
File "/root/HotWalletBot/games/seed.py", line 265, in main
claimer.run()
File "/root/HotWalletBot/games/claimer.py", line 166, in run
wait_time = self.full_claim()
File "/root/HotWalletBot/games/seed.py", line 100, in full_claim
self.launch_iframe()
File "/root/HotWalletBot/games/claimer.py", line 865, in launch_iframe
self.send_start(self.step)
File "/root/HotWalletBot/games/claimer.py", line 971, in send_start
if not attempt_send_start():  # Retry after restoring backup
File "/root/HotWalletBot/games/claimer.py", line 957, in attempt_send_start
chat_input.send_keys("/start")
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/webelement.py", line 231, in send_keys
self._execute(
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/webelement.py", line 395, in _execute
return self._parent.execute(command, params)
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py", line 354, in execute
self.error_handler.check_response(response)
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/errorhandler.py", line 229, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: stale element not found
(Session info: chrome=128.0.6613.137); For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#stale-element-reference-exception
Stacktrace:
#0 0x56362c7fa34a
#1 0x56362c4ded70
#2 0x56362c4eef51
#3 0x56362c4e53fc
#4 0x56362c4e3719
#5 0x56362c4e680f
#6 0x56362c4e68bc
#7 0x56362c52e5a2
#8 0x56362c52e633
#9 0x56362c525148
#10 0x56362c552532
#11 0x56362c5220e8
#12 0x56362c5526fe
#13 0x56362c57062e
#14 0x56362c5522d3
#15 0x56362c520325
#16 0x56362c52132e
#17 0x56362c7c30cf
#18 0x56362c7c7186
#19 0x56362c7b09e7
#20 0x56362c7c7921
#21 0x56362c797cee
#22 0x56362c7e9458
#23 0x56362c7e9658
#24 0x56362c7f8f6d
#25 0x7f79a2821ac3
Traceback (most recent call last):
File "/root/HotWalletBot/games/seed.py", line 268, in
main()
File "/root/HotWalletBot/games/seed.py", line 265, in main
claimer.run()
File "/root/HotWalletBot/games/claimer.py", line 166, in run
wait_time = self.full_claim()
File "/root/HotWalletBot/games/seed.py", line 100, in full_claim
self.launch_iframe()
File "/root/HotWalletBot/games/claimer.py", line 865, in launch_iframe
self.send_start(self.step)
File "/root/HotWalletBot/games/claimer.py", line 971, in send_start
if not attempt_send_start():  # Retry after restoring backup
File "/root/HotWalletBot/games/claimer.py", line 958, in attempt_send_start
chat_input.send_keys(Keys.RETURN)
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/webelement.py", line 231, in send_keys
self._execute(
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/webelement.py", line 395, in _execute
return self._parent.execute(command, params)
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/webdriver.py", line 354, in execute
self.error_handler.check_response(response)
File "/root/HotWalletBot/venv/lib/python3.10/site-packages/selenium/webdriver/remote/errorhandler.py", line 229, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.StaleElementReferenceException: Message: stale element reference: stale element not found
(Session info: chrome=128.0.6613.137); For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#stale-element-reference-exception
Stacktrace:
#0 0x555b8f65034a
#1 0x555b8f334d70
#2 0x555b8f344f51
#3 0x555b8f33b3fc
#4 0x555b8f339719
#5 0x555b8f33c80f
#6 0x555b8f33c8bc
#7 0x555b8f37cbf1
#8 0x555b8f3a8532
#9 0x555b8f3780e8
#10 0x555b8f3a86fe
#11 0x555b8f3c662e
#12 0x555b8f3a82d3
#13 0x555b8f376325
#14 0x555b8f37732e
#15 0x555b8f6190cf
#16 0x555b8f61d186
#17 0x555b8f6069e7
#18 0x555b8f61d921
#19 0x555b8f5edcee
#20 0x555b8f63f458
#21 0x555b8f63f658
#22 0x555b8f64ef6d
#23 0x7fa024173ac3
so i think the sessions is not active again right?

Sounds like the script is not able to read the chat, possibly due to the session being logged out. I added the OTP script to the standard repository, so you can launch it with:
./launch.sh otp

Although in fairness,you looked to have created the script correctly, but it is not receiving the data it expects. Have you tested it on another account that you know to be working?
As always, you need to activate the debugging screenshots to see what's happening (as described in the Troubleshooting guide). Here are mine as an example:
In-game trouble shooting screenshot from ./screenshots/BNB-Cold:Wallet1/01_MonElem-grab-the-last-OTP.png

Screenshot of the script at the same point:

As you can see, the screenshot of the Telegram interface in the virtual browser shows two visible Login code:, the final one is 69341, which is correctly collected by the script and shown in the screenshot.


Google geocoder only using short names for state/country

(This has only become apparent with the fix to Google geocoder in 3.90)
Problem as observed:
When a user sets an Account's BillingCountry to Belgium, the country field shortly thereafter changes to BE.  If the user then "corrects" the address, it changes back once again.  Since we have external integrations and reports that rely on the values of BillingAddress, this really makes things difficult.  In an extreme case (e.g., "Uttar Pradesh, India", for American users), the textual data becomes opaque for all purposes, even mailing labels (USPS will not deliver to the country of India, but to the state of Indiana).
Problem diagnosis:
Then, ADDR_GoogleGeoAPI_Validator#verifyAddress sets the new Address__c record's MailingCountry__c and MailingState__c to add.short_name (lines 188-192) which forces "Belgium" to "BE" (or "Arkansas" to "AR", or "Uttar Pradesh" to "UP").  Then (since that newly added address is default), that address is used to set BillingAddress.
Suggestions:
There are several pieces I'd recommend changing.  I don't know if these should be global changes or just configurable.

I would like to also keep long names and ISO codes in my Address__c records for search purposes (perhaps add another two fields to Address__c for the long names)
I would like to keep long countries and states in my Mailing/BillingAddress fields.  It's fine if that's not the default option, though I do think that Uttar Pradesh, India, would be an issue for many of your US users.

Work around:
My current work-around is to turn off geocoding for Organizational Account Addresses.  Households will still have illegible addresses, but in my case, that is largely fine.

split off the separate tickets.

Given that there has been no subsequent activity on this Issue for the past 4 years, we are going to assume this is no longer occurring.


Add metadata for backend so that we know root/bucket and so on

It will also enable implementing custom traits for backends, so that one can implement custom bulk operations if they wish.


More user feedback for click grid functions

when clicking to 'move' or place the grid box on the left side, it is correctly centering around the courser, but it's just barely misaligned.
(cntl + G)
It's almost as if it's being placed to the center of the mouse, not the point of the mouse.
Maybe backing off the offset by 1 px would do it.

before, it used the top left corner and didn't have the issue. now, it uses the "center" but the center has to be a pixel and, depending on your scaling, it could seem like it is one pixel off for edge cases

tried floor, ceiling, +1 and -1 and they all have the same edge case issue (there just aren't that many pixels in the tile)

It's actually perfect on the right screen, but on the left grid it's slightly off... idk, maybe it's just me

left = grid, right = feature
the left is perfect and the right is slightly off, correct?
if so, then it is not just you

No, it's opposite, the inspection viewer on the right is correct.
The left side grid array is slightly off

https://user-images.githubusercontent.com/19335151/184418757-5d8b8d2c-449f-4b63-88d1-238959954553.mp4
left feels good, right is understandably off (but that is what I want to make "feel" better without actually changing the outcome)

I did a good amount of testing here (I even dabbled with click and drag/resize functions), but I can't seem to make this "feel" better without redoing the entire form.

Well... it's good enough. If it can't be easily fixed then oh well


Support for recognizing guard clauses

I'm confident that this has been brought up before at some point but I couldn't find an issue for it.
Currently, luau doesn't recognize guard clauses when refining types:
local myString: string? = "My string"
if not myString then
	return
end
print(#myString) -- type warning, because luau thinks myString may be nil, even though this is refined in the above guard clause

I use guard clauses all over the place, including continue and rarely break, and this is currently one of the biggest annoyances I have writing code with the typechecker on. This would be extremely nice to have, especially now that typing has become generally more consistent and therefore more powerful.

I'm confident that this has been brought up before at some point but I couldn't find an issue for it.

Yes, this is a duplicate of https://github.com/Roblox/luau/issues/356 and https://github.com/Roblox/luau/issues/670
We are working to fix this, but the full system that handles this will need some time to get finished.

Closing in favor of #356 which is the main tracking ticket.


Integrate GPU Attribute filtering with GPUGridAggregator

Right now GPU Attribute filtering is performed by Layer system setting up required extra attributes and injecting required shader modules.  Aggregation layers , GridLayer (CPUGridLayer and GPUGridLayer), ContourLayer and ScreenGridLayer, use GPUGridAggregator but it handles attributes directly and doesn't use AttributeManger.

[x] ScreenGridLayer

[x] Simplify the layer by merging WebGL1 and WebGL2 versions.

[X] All aggregation layers must be composite layers

[x] Make ScreenGridLayer a composite layer which produces attribute Buffers and provides them to sub layer (cell) which actually renders the cell.
[x] Verify other aggregation layers to make sure, Buffer attributes are not directly updated instead provided to sub layers.

[x] New composite layers AggregationLayer and GridAggregationLayer.

[x] Prepare GPUGridAggregator and Utility methods to accept attributes from AttributeManager.
[x] Update Unit tests.
[x] Start with one layer (GPUGridLayer) and Integrate AttributeManager.
[x] Extract AttributeManager integration code into new composite super layers.
[x] Make all aggregation layers extend this new Composite layer.

[x] GPU Data Filtering (extension)

[x] GPUGridLayer
[x] ContourLayer
[x] ScreenGridLayer

[ ] CPU Aggregation

[x] Write RFC for CPU Aggregation refactor/integration
[x] Remove CPU Aggregation code from GPUGridAggregator.
[x] Update CPU Aggregation to consume data from Attribute Manager.
[x] Update all layer's CPU Aggregation interface

[x] HexagonLayer
[x] CPUGridLayer
[x] ScreenGridLayer (CPU fallback case WebGL1)
[ ] ContourLayer (CPU fallback case WebGL1)

[ ] Data filtering for CPU Aggregation cases

[ ] Investigate kepler.gl data filtering and map it to deck.gl
[ ] Investigate and develop any fallbacks for cases that are not supported by deck.gl GPU Data filtering.

[x] Cleanup FP64 aggregation flag

[ ] Misc

[ ] Remove getFloatTexture usage with inline Textuer2D creation (see: #3681
[ ] Attribute.value may not be Typed array always (like when it is a constant or Buffer object), add an API to access typed array to Attribute class to access typed arrays. (may be getData()) #3956
[ ] AttributeManager: add support to calculate bounding box for an Attribute. (#3828), once done data parsing can be completely removed from aggregation layers.
[ ] Add support for LayerExtension to verify if it needs a redraw (#3844)
[ ] Handle position transitions for all aggregation layers (both CPU and GPU paths). (#3986)

All remaining items are tracked separately, closing.


wasi-http: Implement http-error-code, and centralize error conversions

Implement the body of http-error-code, and add a test that shows its use when writing too much. This functionality was missing from #7434.
Additionally, add some functions in wasi-http for converting from hyper::Error and http::Error to the new ErrorCode variant. These functions log the error received as a warning, and return the translated error to the guest.

@elliottt is this something that should be backported to Wasmtime 15?


node2nix: Remove node_ prefix in buildNodePackage

Motivation for this change
Fixes #127137
This greatly improves compatibility with repology.org. As a side effect, more packages
will be supported by automatic update tools
Things done

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

[ ] 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/)
21.11 Release Notes (or backporting 21.05 Relase 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129697 at ee9fc091 run on x86_64-linux 1

10 packages failed to build:

discourse
python39Packages.batchspawner
python39Packages.dockerspawner
python39Packages.jupyterhub
python39Packages.jupyterhub-ldapauthenticator
python39Packages.jupyterhub-systemdspawner
python39Packages.jupyterhub-tmpauthenticator
python39Packages.oauthenticator
remarkjs
vimPlugins.coc-imselect

6 packages skipped due to time constraints:

emojione
imgbrd-grabber
iosevka
lumo
sage
sageWithDoc

122 packages built successfully:

airfield
antora
balanceofsatoshis
base16-builder
bat-extras.prettybat
bitwarden-cli
castnow
create-cycle-app
cryptpad
elmPackages.create-elm-app
elmPackages.elm-analyse
elmPackages.elm-coverage
elmPackages.elm-doc-preview
elmPackages.elm-language-server
elmPackages.elm-live
elmPackages.elm-optimize-level-2
elmPackages.elm-review
elmPackages.elm-test
elmPackages.elm-upgrade
elmPackages.elm-verify-examples
elmPackages.elm-xref
epgstation
fast-cli
flood
fx
google-clasp
gtop
hueadm
image_optim
imapnotify
joplin
ldgallery
lessc
mastodon-bot
matrix-appservice-irc
matrix-appservice-slack
mirakurun
mx-puppet-discord
n8n
netlify-cli
nixos-install-tools
nixui
parity-ui
pm2
postcss-cli
pscid
pulp
purescript-psa
pyright
python38Packages.batchspawner
python38Packages.dockerspawner
python38Packages.jupyterhub
python38Packages.jupyterhub-ldapauthenticator
python38Packages.jupyterhub-systemdspawner
python38Packages.jupyterhub-tmpauthenticator
python38Packages.oauthenticator
redoc-cli
shout
slack
sloc
spacegun
styx
teams
teck-programmer
teleprompter
thelounge
timedoctor
triton
uchiwa
vimPlugins.YouCompleteMe
vimPlugins.coc-clangd
vimPlugins.coc-cmake
vimPlugins.coc-css
vimPlugins.coc-diagnostic
vimPlugins.coc-emmet
vimPlugins.coc-eslint
vimPlugins.coc-explorer
vimPlugins.coc-git
vimPlugins.coc-go
vimPlugins.coc-highlight
vimPlugins.coc-html
vimPlugins.coc-java
vimPlugins.coc-jest
vimPlugins.coc-json
vimPlugins.coc-lists
vimPlugins.coc-markdownlint
vimPlugins.coc-metals
vimPlugins.coc-pairs
vimPlugins.coc-prettier
vimPlugins.coc-pyright
vimPlugins.coc-python
vimPlugins.coc-r-lsp
vimPlugins.coc-rls
vimPlugins.coc-rust-analyzer
vimPlugins.coc-smartf
vimPlugins.coc-snippets
vimPlugins.coc-solargraph
vimPlugins.coc-stylelint
vimPlugins.coc-tabnine
vimPlugins.coc-texlab
vimPlugins.coc-tslint
vimPlugins.coc-tslint-plugin
vimPlugins.coc-tsserver
vimPlugins.coc-vetur
vimPlugins.coc-vimlsp
vimPlugins.coc-vimtex
vimPlugins.coc-wxml
vimPlugins.coc-yaml
vimPlugins.coc-yank
vscode-extensions.matklad.rust-analyzer
vscode-extensions.ms-python.vscode-pylance
vscode-extensions.vadimcn.vscode-lldb
wasm-strip
wasm-text-gen
wast-refmt
webassemblyjs-cli
webassemblyjs-repl
whitebophir
wring
yaml-language-server
ycmd
zerobin

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.

Shouldn't this be changed in node2nix itself, instead?

Yes, it should be.

The thing is, node2nix development sadly is kind of stalled at the moment.

You can do a PR and we fetch that instead.

I opened https://github.com/svanderburg/node2nix/pull/243 . Should I override the source or apply the change as patch?

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

2 packages marked as broken and skipped:

remarkjs
vimPlugins.coc-imselect

2 packages blacklisted:

tests.nixos-functions.nixos-test
tests.writers

1 package failed to build:

nixos-install-tools

135 packages built:

airfield
antora
balanceofsatoshis
base16-builder
bat-extras.prettybat
bitwarden-cli
castnow
create-cycle-app
cryptpad
discourse
elmPackages.create-elm-app
elmPackages.elm-analyse
elmPackages.elm-coverage
elmPackages.elm-doc-preview
elmPackages.elm-language-server
elmPackages.elm-live
elmPackages.elm-optimize-level-2
elmPackages.elm-review
elmPackages.elm-test
elmPackages.elm-upgrade
elmPackages.elm-verify-examples
elmPackages.elm-xref
emojione
epgstation
fast-cli
flood
fx
google-clasp
gtop
hueadm
image_optim
imapnotify
imgbrd-grabber
iosevka
joplin
ldgallery
lessc
lumo
mastodon-bot
matrix-appservice-irc
matrix-appservice-slack
mirakurun
mx-puppet-discord
n8n
netlify-cli
nixui
parity-ui
pm2
postcss-cli
pscid
pulp
purescript-psa
pyright
python38Packages.batchspawner
python38Packages.dockerspawner
python38Packages.jupyterhub
python38Packages.jupyterhub-ldapauthenticator
python38Packages.jupyterhub-systemdspawner
python38Packages.jupyterhub-tmpauthenticator
python38Packages.oauthenticator
python39Packages.batchspawner
python39Packages.dockerspawner
python39Packages.jupyterhub
python39Packages.jupyterhub-ldapauthenticator
python39Packages.jupyterhub-systemdspawner
python39Packages.jupyterhub-tmpauthenticator
python39Packages.oauthenticator
redoc-cli
sage
sageWithDoc
shout
slack
sloc
spacegun
styx
teams
teck-programmer
teleprompter
thelounge
timedoctor
triton
uchiwa
vimPlugins.YouCompleteMe
vimPlugins.coc-clangd
vimPlugins.coc-cmake
vimPlugins.coc-css
vimPlugins.coc-diagnostic
vimPlugins.coc-emmet
vimPlugins.coc-eslint
vimPlugins.coc-explorer
vimPlugins.coc-git
vimPlugins.coc-go
vimPlugins.coc-highlight
vimPlugins.coc-html
vimPlugins.coc-java
vimPlugins.coc-jest
vimPlugins.coc-json
vimPlugins.coc-lists
vimPlugins.coc-markdownlint
vimPlugins.coc-metals
vimPlugins.coc-pairs
vimPlugins.coc-prettier
vimPlugins.coc-pyright
vimPlugins.coc-python
vimPlugins.coc-r-lsp
vimPlugins.coc-rls
vimPlugins.coc-rust-analyzer
vimPlugins.coc-smartf
vimPlugins.coc-snippets
vimPlugins.coc-solargraph
vimPlugins.coc-stylelint
vimPlugins.coc-tabnine
vimPlugins.coc-texlab
vimPlugins.coc-tslint
vimPlugins.coc-tslint-plugin
vimPlugins.coc-tsserver
vimPlugins.coc-vetur
vimPlugins.coc-vimlsp
vimPlugins.coc-vimtex
vimPlugins.coc-wxml
vimPlugins.coc-yaml
vimPlugins.coc-yank
vscode-extensions.matklad.rust-analyzer
vscode-extensions.ms-python.vscode-pylance
vscode-extensions.vadimcn.vscode-lldb
wasm-strip
wasm-text-gen
wast-refmt
webassemblyjs-cli
webassemblyjs-repl
whitebophir
wring
yaml-language-server
ycmd
zerobin

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 129697 run on x86_64-linux 1

2 packages marked as broken and skipped:

remarkjs
vimPlugins.coc-imselect

2 packages blacklisted:

tests.nixos-functions.nixos-test
tests.writers

7 packages failed to build and already failed to build on hydra master:

python38Packages.batchspawner: log was empty
python38Packages.dockerspawner: log was empty
python38Packages.jupyterhub: log was empty
python38Packages.jupyterhub-ldapauthenticator: log was empty
python38Packages.jupyterhub-systemdspawner: log was empty
python38Packages.jupyterhub-tmpauthenticator: log was empty
python38Packages.oauthenticator: log was empty

13 packages failed to build and are new build failures:

discourse: log was empty
elmPackages.elm-coverage: log was empty
elmPackages.elm-verify-examples: log was empty
fast-cli: log was empty
image_optim: log was empty
iosevka: log was empty
ldgallery: log was empty
lumo: log was empty
nixos-install-tools: log was empty
sage: log was empty
sageWithDoc: log was empty
styx: log was empty
timedoctor: log was empty

116 packages built:

airfield
antora
balanceofsatoshis
base16-builder
bat-extras.prettybat
bitwarden-cli
castnow
create-cycle-app
cryptpad
elmPackages.create-elm-app
elmPackages.elm-analyse
elmPackages.elm-doc-preview
elmPackages.elm-language-server
elmPackages.elm-live
elmPackages.elm-optimize-level-2
elmPackages.elm-review
elmPackages.elm-test
elmPackages.elm-upgrade
elmPackages.elm-xref
emojione
epgstation
flood
fx
google-clasp
gtop
hueadm
imapnotify
imgbrd-grabber
joplin
lessc
mastodon-bot
matrix-appservice-irc
matrix-appservice-slack
mirakurun
mx-puppet-discord
n8n
netlify-cli
nixui
parity-ui
pm2
postcss-cli
pscid
pulp
purescript-psa
pyright
python39Packages.batchspawner
python39Packages.dockerspawner
python39Packages.jupyterhub
python39Packages.jupyterhub-ldapauthenticator
python39Packages.jupyterhub-systemdspawner
python39Packages.jupyterhub-tmpauthenticator
python39Packages.oauthenticator
redoc-cli
shout
slack
sloc
spacegun
teams
teck-programmer
teleprompter
thelounge
triton
uchiwa
vimPlugins.YouCompleteMe
vimPlugins.coc-clangd
vimPlugins.coc-cmake
vimPlugins.coc-css
vimPlugins.coc-diagnostic
vimPlugins.coc-emmet
vimPlugins.coc-eslint
vimPlugins.coc-explorer
vimPlugins.coc-git
vimPlugins.coc-go
vimPlugins.coc-highlight
vimPlugins.coc-html
vimPlugins.coc-java
vimPlugins.coc-jest
vimPlugins.coc-json
vimPlugins.coc-lists
vimPlugins.coc-markdownlint
vimPlugins.coc-metals
vimPlugins.coc-pairs
vimPlugins.coc-prettier
vimPlugins.coc-pyright
vimPlugins.coc-python
vimPlugins.coc-r-lsp
vimPlugins.coc-rls
vimPlugins.coc-rust-analyzer
vimPlugins.coc-smartf
vimPlugins.coc-snippets
vimPlugins.coc-solargraph
vimPlugins.coc-stylelint
vimPlugins.coc-tabnine
vimPlugins.coc-texlab
vimPlugins.coc-tslint
vimPlugins.coc-tslint-plugin
vimPlugins.coc-tsserver
vimPlugins.coc-vetur
vimPlugins.coc-vimlsp
vimPlugins.coc-vimtex
vimPlugins.coc-wxml
vimPlugins.coc-yaml
vimPlugins.coc-yank
vscode-extensions.matklad.rust-analyzer
vscode-extensions.ms-python.vscode-pylance
vscode-extensions.vadimcn.vscode-lldb
wasm-strip
wasm-text-gen
wast-refmt
webassemblyjs-cli
webassemblyjs-repl
whitebophir
wring
yaml-language-server
ycmd
zerobin

After this PR, I'm getting the following error on darwin
error: hash mismatch in fixed-output derivation '/nix/store/rd4pn8wi4idacrpnixrvybqwm10750ad-58736093161f2d237c17e75a96529b018cd0ac64.patch.drv':
         specified: sha256-1nyuys8crzcICesAYAtAwlv7bjb4lu2U/5Bco7DDIbE=
            got:    sha256-UAw1SC/RdRgcy602bNOPLxacOy482larfOYlNgA6Lmo=
error: 1 dependencies of derivation '/nix/store/j72qkb6avlk8bi3lx9pcg5y8j7isgrxv-source-patched.drv' failed to build
error: 1 dependencies of derivation '/nix/store/9s09w9ygs7nyiyq42cidwn6bagm5c70q-node2nix-1.9.0.drv' failed to build

I'm not sure if that is expected.

I get a similar error on NixOS:
hash mismatch in fixed-output derivation '/nix/store/473jnv3r45c5wnn53hn69qbnqpfaib5d-58736093161f2d237c17e75a96529b018cd0ac64.patch':
  wanted: sha256:1c91qfqa6p4hzyafv5pq6rpgnny2805n007b1443gbqwrz5awz6n
  got:    sha256:0sif7803c9g6gjmmdniw5qxrq5igiz9nqdmdrcf1hxfi5x43a32h

I too get the hashes errors, fix is in https://github.com/NixOS/nixpkgs/pull/130719 .

I'm sorry for the breakage and thank you @doronbehar for the fix.

On my part I'm grateful that you took the time to make the change! ❤


Without Watermark?

Hey..
Its was great repository.
What is the response from get video and also the challenge without a watermark?

I'm not sure I follow. Are you asking for how to download a video without a watermark? As far as I know, the watermark that appears on the screen throughout the video cannot be removed, but the instructions in the documentation for downloading a video will give you a video without the ending watermark/panel.
If you're looking for more information about the data returned by the library, it's laid out in the API reference.
Can you clarify what you're looking for?

Sorry for the less questions.
I mean, can you add a TT video scraper without a watermark?

My library cannot download a video without the watermark that is placed over the video during the video. A link to such a version of the video is not provided directly from TikTok, so I'm not sure how this could be done without going to 3rd party resources like https://snaptik.app/en.
A solution that utilizes this specific 3rd party resource is linked in https://github.com/davidteather/TikTok-Api/issues/628.
If all you want is to download videos from TikTok without watermarks, I'd suggest you go directly to a tool like SnapTik or make use of something that pipes videos through SnapTik.
I will not be implementing anything into TikTokPy that removes the watermarks on videos. I think it's important to give credit to whomever created the video.

Okay.
Thanks for fast reply.


Add info how to enable serial in fw for pikvm on novacustom

@macpijan I have added changes with regards to your comments

fixed precommit issues at: 72d963c922e3e878a7e182ee485e3c8521f7cf46


sampling time and gain in color sensor

The color sensor I'm using has a programmable GAIN (1x, 2x, 4x, 8x I think) and sampling time (2.4ms - 700ms). I wonder if many other color sensors would have such a thing? Should we add that as optional configuration registers? I was thinking gain: u16.16 and sampling_time: u32 us. If the values the user gets are out of range, they could fiddle with these settings.

I guess we could instead have a generic sensitivity: u16.16? That could somehow translate to gain and sampling time.

I think a generic option would be better? I assume you’re thinking in the sensor base class?
James

From: Michał Moskal @.>
Sent: Friday, August 6, 2021 7:15:27 PM
To: microsoft/jacdac @.>
Cc: James Devine @.>; Assign @.>
Subject: Re: [microsoft/jacdac] sampling time and gain in color sensor (#554)
I guess we could instead have a generic sensitivity: u16.16? That could somehow translate to gain and sampling time.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fjacdac%2Fissues%2F554%23issuecomment-894434287&data=04|01|t-jamdev%40microsoft.com|2aefe060c10544bee5bf08d959062ae6|72f988bf86f141af91ab2d7cd011db47|1|0|637638705403926321|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ObahRieKdIMZeqTTHE7kK0fYr6CO%2BRgciFGlIJTQi24%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABEF4KIZVMTR2HMC5DLKXW3T3QRD7ANCNFSM5BWL6KYA&data=04|01|t-jamdev%40microsoft.com|2aefe060c10544bee5bf08d959062ae6|72f988bf86f141af91ab2d7cd011db47|1|0|637638705403936315|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Z%2BUdr5iRcUTs7FtnPEJIYb18%2BYKncR7mVkIbQMr%2Fcts%3D&reserved=0.


nsc-events-9-bug-518-invalid-start-and-end-times

resolves #518
This PR fixes the start and end time picker fields error. Events whose start and end times are formatted with a space between the time value and the time of day are not parsed properly and so the times must be formatted as such: "XX:XXAM" or "XX:XXPM"
"10:00 AM" -> "10:00AM"
The function I used to remove the whitespace uses a common regex pattern for removing whitespace.
https://github.com/SeattleColleges/nsc-events-nextjs/assets/13278479/172bb87d-585a-4a7e-8482-bfea84779fe0

@heosman I can take a look at that and see if its related to this one and if not I can pick up the other one

@heosman I can take a look at that and see if its related to this one and if not I can pick up the other one

@cshimm I checked on the main branch and it seems to be an issue there too, so don't think it's this PR. I've created the issue so feel free to assign yourself.


Splash Screen too fast at Release Mode

Hello, I tried your package but when i run it, Splash Screen show too fast then a blank screen appears like glitch blank with interval 1 second before the first page is run. Thanks for your package :)

+1

Probably this is the solution: #54

Has anyone solved the issue of fading of splash screen fastly in release mode?

This package is designed to display a splash screen while the Flutter architecture is loading.  If the splash screen shows too fast, that means that your device is loading the Flutter architecture quickly, which is a good thing.  If you have a subsequent blank screen, that is caused by activity that is taking place within your flutter app.  You can resolve this by placing a second splash screen in your flutter app that displays while resources are loading in your flutter app.

This package is designed to display a splash screen while the Flutter architecture is loading.  If the splash screen shows too fast, that means that your device is loading the Flutter architecture quickly, which is a good thing.  If you have a subsequent blank screen, that is caused by activity that is taking place within your flutter app.  You can resolve this by placing a second splash screen in your flutter app that displays while resources are loading in your flutter app.


Added README.md

I have not added a screenshot but added a line describing what the user sees in the modeline.

PR related to #3

Looks great, thank you for making it!


fix(docs): firewall and security recommendations

Closes: #52
Description

description about firewall config added in join testnet guide
validator security guide updated

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added  relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

For admin use:

[ ] Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
[ ] Reviewers assigned
[ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

I don't see specific firewall rules recommendation. Which ports should be open, which should be closed.
Operators should be able to find and read this info in a separate docs page.


Build Docs error : helidon-common: Compilation failure

Hi,
I'm trying to build docs for translation, but I got the following error.
Would you suggest how to solve the matter?
Thanks.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.583 s
[INFO] Finished at: 2024-01-10T16:04:26+09:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) on project helidon-common: Compilation failure
[ERROR] error: invalid flag: -proc:full

...
I'm using the following maven and java versions:
$ mvn -version
Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
Maven home: /opt/apache-maven
Java version: 17.0.9, vendor: Private Build, runtime: /usr/lib/jvm/java-17-openjdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "<IP_ADDRESS>-microsoft-standard-wsl2", arch: "amd64", family: "unix"

The main branch is used for the 4.x codeline currently which requires JDK21.
Also the steps in the README apply to the docs directory.
I.e.
# do a full build first
mvn install -DskipTests

# then build the docs
cd docs
mvn package -Pjavadocs

Thanks, some things have been built with JDK21.
But nothing is displayed on the browser, because the paths are described in absolute paths, like:
  <script src="/components/mainView.js"></script>
  <script src="/components/docView.js"></script>
  <script src="/components/defaultView.js"></script>

I need to publish translated version for v4 in relative path, like v3:
https://oracle-japan-oss-docs.github.io/helidon/docs/v3/#/about/introduction
If you could instruct how to solve it, it would be great.
Also,  javadoc was not build with the following messages, but it is ok, since they could be retrieved by wget:
[WARNING] The requested profile "javadocs" could not be activated because it does not exist.

Thanks, Thibault san.

V4 docs as they are require a server, they cannot be served with a simple static server like GitHub pages as-is.
You will need to edit the generated files to support history mode and edit the paths to not be absolute.
I.e. the inverse of these changes: https://github.com/helidon-io/helidon-build-tools/pull/1001/files#diff-e82ec35b1c225780e0235fd50a8a36bc236086b79a9fdc49c88b617987fd4be0R82

Thanks,  I'll edit them as suggested.


Help Scout is saying good-bye to legacy Mailbox API 1.0 on June 6th, 2019

This project is built on Help Scout’s Mailbox API 1.0. We announced the retirement of Mailbox API 1.0 last year and will end support on June 6, 2019.  To ensure that all integrations continue to function properly, they must be moved to Mailbox API 2.0. If you have any questions about how to migrate to the new API, please reach out to the Help Scout team. We’re here to help!

Love this extension, would love to see 2.0 support.

Any word on this? API 1.0 officially shut off and the extension is broken now.

I'm working on updating it.  I'm hoping to use my downtime this holiday season to get it finished up.  Javascript is not my first language so I'm a little slow but I have working code in PowerShell that I am using as a guide.


Removing SLPDB and v4 routes

:tada: This PR is included in version 2.1.0 :tada:
Your semantic-release bot :package::rocket:


Cannot access response data on Indices.GetAlias API

Elastic.Clients.Elasticsearch version:
8.0.0-rc.2
Elasticsearch version:
8.x.x
.NET runtime version:
6.0
Operating system version:
Windows 11
Description of the problem including expected versus actual behavior:
According to the list of supported API's the Indices.GetAlias is supported in the current version. But no data is accessible in the response (AliasResponse), only whether the response is valid (IsValidResponse) along with Error, Warnings, DebugInformation and API Call Details.
As i read the specifications a dictionary should be available:
body: Dictionary<IndexName, IndexAliases>
Which matches the data returned from a direct HTTP request to the API endpoint.
If i look into the AliasResponse through debugging there is a non-accessible BackingDictionary that holds the values of the response, but as this is not accessible it is not of much help.
So for now this method is not of much use other than checking for existence, which already has its own API.
Steps to reproduce:

Make a call to ES 8 using esClient.Indices.GetAliasAsync()
Inspect the returned AliasResponse, it has no accessible Dictionary<IndexName, IndexAliases>

Expected behavior
Response should contain an accessible dictionary of IndexName, IndexAliases

Hi, @Alkaersig.
Thanks for raising this. Indeed, this looks like a bug in the code generator, which isn't emitting the public property to access the backing dictionary. This affects most types deriving from DictionaryResponse:

GetAliasResponse
GetFieldMappingResponse
GetIndexResponse
GetTemplateResponse

The solution is to emit the appropriate property during code-generation or to manually add the properties and accessor methods as we do for GetMappingResponse.
We'll aim to fix this for the next patch release.

@Alkaersig This has been addressed in 8.0.2, which we released today.

@stevejgordon thanks Steve! I updated our solution to use version 8.0.2 and can confirm that it works as expected.


RuntimeError: Error in faiss::(anonymous namespace)::FileIOReader::FileIOReader(const char *) at index_io.cpp:136: Error: 'f' failed: could not open ./index_lib/grid_populated.index for reading: No such file or directory

hi，I just wanna run the demo_test, but ,here are some problems.
RuntimeError: Error in faiss::(anonymous namespace)::FileIOReader::FileIOReader(const char *) at index_io.cpp:136: Error: 'f' failed: could not open ./index_lib/grid_populated.index for reading: No such file or directory
so could you please give me your ./index_lib/grid_populated.index.
Thanks

python demo_train.py -d ./demo_data/grid/normal_data -c grid


SQL Server scaffolding generates invalid anonymous types for indexes (rc1-final)

I use the NORTHWND database restored from https://northwinddatabase.codeplex.com, and use the following command to scaffold entity classes:
dnx EntityFramework.Commands dbcontext scaffold "data source=.\SQLEXPRESS;initial catalog=NORTHWND;integrated security=True" EntityFramework.MicrosoftSqlServer -a -c NorthwindContext -o Models\Northwind

Design package is EntityFramework.MicrosoftSqlServer.Design 7.0.0-rc1-final
Generated classes fail to compile with "An anonymous type cannot have multiple properties with the same name".
Problematic source lines:
entity.HasIndex(e => new { e.CompanyName, e.CompanyName }).HasName("CompanyName");
entity.HasIndex(e => new { e.PostalCode, e.PostalCode, e.PostalCode }).HasName("PostalCode");

Hi Aleksey. Thanks for reporting this. It looks like there's a problem in the code which uniquifies property names and/or creates indexes. We'll look into it.

This was a consequence of us conflating indexes which had the same name but were on different tables. This was fixed by #3934.

Related stackoverflow question: Entity Framework 7: An anonymous type cannot have multiple properties with the same name


South's --auto doesn't work for ManyToManyField -> SortedManyToManyField

If I have a Poll model with a questions = models.ManyToManyField(Question), and I change the field into a SortedManyToManyField, South doesn't detect the change:
$ ./manage.py schemamigration --auto polls
Nothing seems to have changed.

This is Django pre-1.5, django-sortedm2m 0.4.0 and South 0.7.6.

@gorandev What is the status for this? Is there something I could help you with?

@rolandgeider I have to document it and add some tests! Can you help with that? :)

@gorandev I can do the documentation, not sure about the tests.

I have opened a pull request (#42) with my first attempt at documenting this, feedback welcome

How's this going?

@outime I have started working on the tests on my branch, but they are not ready yet

Thanks @rolandgeider for making a good start on this! I finished of the work and added tests for the AlterSortedManyToManyField operation. The operation has been released as part of the 0.9.0 release: https://pypi.python.org/pypi/django-sortedm2m/

Cool, thanks!

+1

I tried @akaihola's approach for getting a south migration to add sort_value, but while the migration isn't reporting an error the column doesn't appear to exist after the migration runs.

@georgedorn could you paste the forwards and backwards method of your migration here so that we can see what you have by now?


Add vue-i18n to manage languages

[x] Add vue-i18n
[x] Generate dictionary
[x] Detect user language

Pending:

Detect user language
Generate dictionary

It is necessary to review the texts to be translated and add them to the dictionary.


Wrong settings access for exposeHeaders

In setExposeHeaders the associative array settings is accessed with arrow operator:
$this->settings->exposeHeaders (lines 26 - 27).
Should not be $this->settings['exposeHeaders']?

@robycup Thanks for the PR.
Published as v0.0.3.


[Rmote Store] Run integ tests with segrep and remote store enabled

Is your feature request related to a problem? Please describe
We run integ tests without segrep or remote store enabled defaulting to docrep, which might create regression and mostly tech debt during release activities where we need to depend on manual sign-offs.
Describe the solution you'd like
Given the rate of changes we make we need to enable running randomised testing on decrep/segrep/remote store modes to improve code fidelity.
Related component
Storage
Describe alternatives you've considered
No response
Additional context
No response

We run integ tests without segrep or remote store enabled defaulting to docrep

We have added parameterized tests for replication-focused tests to run both docrep and segrep. We've also added randomization to randomly select replication strategy for other tests not focused on replication. @Rishikesh1159 can you provide more detail about where we're at now and the testing you've done with enabling segrep-with-remote-store?

Running Integ Tests with Segment Replication and Remote Store.
Goal : Run integ tests with segrep and remote store enabled.
Problem : We have two problems to acheive our goal:
1.  Waiting after refresh : After a refresh, we need to wait some time for replicas to catch up with primary shards. The tests will fail with assertion on replica shard before it has caught up with primary.
2. Running all integ Tests : Every Integ Test is different, so there is no single framework for us to follow and enable segrep for all Integ Test at once. There are certain tests that test the behaviour not supported by segrep in this case those tests will fail if we run them with segment replication enabled.
Plan to Overcome Problems :
1. Waiting after refresh :
→ To overcome this problem we have introduced a new method called refreshAndWaitForReplication .
→ This refreshAndWaitForReplication will be used after an indexing operation, so with this method we refresh and then wait for replicas to catch up. This way only any assertions further made in test will be done only after replica has caught up.
→ Basically we will need to replace the refresh() call in IntegTest with refreshAndWaitForReplication .
2. Running all integ Tests :
Every Integ Test that we want to run with segrep/remote-store can be divided into below 4 categories:

A. Critical Tests related to segrep/remote-store :

* The tests which are critical to and directly tests behaviour of segrep/remote-store can be put in this category.

* These are tests which are already exists before and we want run them with both segrep and docrep or remote-store/non remote-store.

* That means we need to run these critical test twice, once with segrep and another with docrep.

* We have used parameterized testing approach for these critical tests to run a single test multiple times with different parameters.

* Example PR: https://github.com/opensearch-project/OpenSearch/pull/11773.

B. Non Crititical Tests :

* The tests which don’t directly test segrep/remote-store behaviour can be put in this category.

* Although these tests don’t test segrep behaviour directly but still can be related to a different feature/operation that is failing because of segrep/remote-store.

* To identify these edge cases and proper working of segrep/remote-store we need to run these non-critical tests with segment replication as well.

* As these are not critical tests we can use randomization here, by randomly picking a replication strategy for test, this way we would cover running tests with both segrep, docrep without running the test multiple times as we did above for critical tests. This increases the test coverage for segrep/remote-store.

* Exaxple PR: https://github.com/opensearch-project/OpenSearch/pull/12297

C. Segrep/Remote-Store Specific Integ Tests :

* These are tests which previously didn’t exists with docrep. These tests are newly created specifically to test certain behaviors of segrep/remote-store.

* As they are tests Specific to segrep/remote-store they are run only once with segrep/remote-store.

* Example Integ Test : [SegmentReplicationIT.java](https://github.com/opensearch-project/OpenSearch/blob/main/server/src/internalClusterTest/java/org/opensearch/indices/replication/SegmentReplicationIT.java)

D. Integ Tests not compatible with segrep/remote-store :

* There are certain Integ tests related to a specific feature/operation that is currently not directly supported by segrep/remote-store. These kind of tests can be put in this category.

* As these Integ tests are not compatible segrep/remote-store we completely avoid/ignore running them with segrep/remote-store enabled.

* Example : [ShrinkIndexIT](https://github.com/opensearch-project/OpenSearch/blob/main/server/src/internalClusterTest/java/org/opensearch/action/admin/indices/create/ShrinkIndexIT.java)

How to a run an existing test with segrep/remote-store :

Step 1 :
* Identify in which of the categories mentioned above does the test comes under.
* If it is a critical test, we need to use parameterization approach. This way the test always runs multiple times with different parameters of segrep/remote-store and docrep. Example:  https://github.com/opensearch-project/OpenSearch/pull/11773.
* If it is a non-critical test, we need to use randomization. Example : https://github.com/opensearch-project/OpenSearch/pull/12297.

Step 2 :
* In the Integ Test replace the usage of refresh() with refreshAndWaitForReplication() .
* If the test uses indexRandom(forceRefresh:true) then indexRandom() internally uses refreshAndWaitForReplication() so we don’t need to worry about refresh in this case.
* For all other remaining type of invocations of refresh like :
    client().prepareIndex("test").setId("1").setSource("field","value1").setRefreshPolicy(RefreshPolicy.IMMEDIATE).get();

we manually we need to call waitForReplication() after a write operation. This way we wait for replica shards to catch up with primary after every write operation.
Step 3 :
* Sometimes few tests in a Integ Test suite make assertions on features/operations which are not compatible with segrep/remote-store. In those cases, we conditionally need to ignore the assertion.
* Example here in [IndexStatsIT](https://github.com/opensearch-project/OpenSearch/blob/3125b948029609f354d3153f8ca6391638daefc7/server/src/internalClusterTest/java/org/opensearch/indices/stats/IndexStatsIT.java#L691), the test testSimpleStats() was asserting on count of write operations on replica shards. But with segment replication these write operation never happens on replica shards, so the test will fail with assertion. To cover such cases we add conditional check before making few assertions.

Step 4 :
* After following all above steps, we have to make sure we run the Integ Test suite for few hundred iterations locally.
* This step is needed to make sure that we are not adding any new flakiness to existing tests.

Current Status :
To reach the goal of Running Integ tests with segrep and remote store enabled. We need completion of following steps:
Step 1 :

Add new refreshAndWaitForReplication()  and waitForReplication()  methods to support tests waiting for replica shards catching up after a write operation.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/11773
Status: COMPLETED.

Step 2 :

Support Parameterization for running critical tests with Segment Replication enabled.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/11773
Status: COMPLETED.

Step 3 :

Support Randomization for running non-critical tests with segment replication enabled randomly.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/12297
Status: COMPLETED.

Step 4 :

Support Parameterization for running critical tests with Remote Store enabled.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/12487
Status: IN-PROGRESS.

Step 5 :

Support Randomization for running non-critical tests with remote store enabled randomly.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/12488
Status: IN-PROGRESS.

Step 6 :

Make of list of existing integ tests which should be critical, non-critical and not compatible with segrep/remote-store. Once the list is made we need to modify each Integ Test to support them run them with segrep/remote-store enabled.
Implemented in PR: N/A
Status: NOT STARTED.

Current Status :
To reach the goal of Running Integ tests with segrep and remote store enabled. We need completion of following steps:
Step 1 :

Add new refreshAndWaitForReplication()  and waitForReplication()  methods to support tests waiting for replica shards catching up after a write operation.
Implemented in PR: [Segment Replication] Add Segment Replication Specific Integration Tests #11773
Status: COMPLETED.

Step 2 :

Support Parameterization for running critical tests with Segment Replication enabled.
Implemented in PR: [Segment Replication] Add Segment Replication Specific Integration Tests #11773
Status: COMPLETED.

Step 3 :

Support Randomization for running non-critical tests with segment replication enabled randomly.
Implemented in PR: [Segment Replication] Add random replication strategy #12297
Status: COMPLETED.

Step 4 :

Support Parameterization for running critical tests with Remote Store enabled.
Implemented in PR: [Remote Store] Add support for Running Parameterized Remote Store Enabled Integration Tests #12487
Status: IN-PROGRESS.

Step 5 :

Support Randomization for running non-critical tests with remote store enabled randomly.
Implemented in PR: [Remote Store] Add support for randomizing Remote Store enabled testing. #12488
Status: IN-PROGRESS.

Step 6 :

Make of list of existing integ tests which should be critical, non-critical and not compatible with segrep/remote-store. Once the list is made we need to modify each Integ Test to support them run them with segrep/remote-store enabled.
Implemented in PR: N/A
Status: NOT STARTED.

Sure @andrross . @Bukhtawar here is current status:
Current Status :
To reach the goal of Running Integ tests with segrep and remote store enabled. We need completion of following steps:
Step 1 :
Add new refreshAndWaitForReplication() and waitForReplication() methods to support tests waiting for replica shards catching up after a write operation.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/11773
Status: COMPLETED.
Step 2 :
Support Parameterization for running critical tests with Segment Replication enabled.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/11773
Status: COMPLETED.
Step 3 :
Support Randomization for running non-critical tests with segment replication enabled randomly.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/12297
Status: COMPLETED.
Step 4 :
Support Parameterization for running critical tests with Remote Store enabled.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/12487
Status: IN-PROGRESS.
Step 5 :
Support Randomization for running non-critical tests with remote store enabled randomly.
Implemented in PR: https://github.com/opensearch-project/OpenSearch/pull/12488
Status: IN-PROGRESS.
Step 6 :
Make of list of existing integ tests which should be critical, non-critical and not compatible with segrep/remote-store. Once the list is made we need to modify each Integ Test to support them run them with segrep/remote-store enabled.
Implemented in PR: N/A
Status: NOT STARTED.


conflict with Boogies Troop Upgrades

when enable both two mods,the game will crash.And log says "No managed frames available."

Interesting, we'll take a look...


Get autokit NPM package under balena scope

Scoping NPM packages prevents supply chain attacks https://github.blog/2021-02-12-avoiding-npm-substitution-attacks/
Added License
and, updated the lockfile to version 2 that comes with npm v7: https://www.abrahamberg.com/blog/npm-package-json-lock-version-1-or-2/
The last commit is to be merged if everyone has started using node v16 (latest LTS)
If not, I can remove it.

@vipulgupta2048 Is the Apache license a default balena thing or did you choose it by yourself?

It has been standard across many repositories

@vipulgupta2048 okay, so please remove the v2 file as we're currently using Node 14, then I'll approve the PR
If we are to make changes to the package name, I believe that the sooner we do it the better

LGTM - I'll need to update the reference to the package name in this leviathan worker PR @vipulgupta2048 https://github.com/balena-os/leviathan-worker/pull/28

@phckopper are we still intending to get this through, if yes. I will update my PR and then open a new PR to update leviathan's reference.

@balena-ci I self-certify!


Add Analysis and Patterns Function

Analyze and assign a pattern of life to devices (perhaps generate a separate database for this?)

Behavior within a Day
- First seen/Last seen (Entire Day)
Odd behaviors
- First seen begins after 7PM
- Weak RSSI for extended period any time (will have to calibrate RSSI locally to see what makes sense)
Display all of this on a 1-month calendar for a single device (and preferably 3 - 5 devices later on, assuming that will take more work)

Are you wanting these patterns for all devices, or would you be ok with adding devices to a "tracking" list?


z.undefined() behaves weird

I was trying to create a schema verifier for one pre-existing interface and stumbled into a weird problem.
This works:

But these aren't:

I find this behavior to be weird. I understand where it might come from, but describing some project types with this library becomes impossible. Also, I would like to point out that in the real project, I have no control over the interface, so this example is from the wild.

Indeed, this is tracked here: https://github.com/colinhacks/zod/issues/635


⚠ RPC server - xDai has degraded performance

In b3ec44a, RPC server - xDai ($XDAI_RPC_URL) experienced degraded performance:

HTTP code: 200
Response time: 371 ms

Resolved: RPC server - xDai performance has improved in 654f3db after 27 minutes.


Document the IAM setup requirements for individual ACK service controllers

We need to create documentation that outlines the prerequisite IAM role/permission setup that needs to occur for ACK service controllers, including a quick scripted demo of setting up IRSA for a Kubernetes cluster and creating (via the AWS console or the aws CLI tool) the required IAM role and permission set for the IAM role associated with the Service Account that is tied to the Pod running the service controller.

I believe this was included as part of the CARM documentation? Does this suffice? https://aws-controllers-k8s.github.io/community/user-docs/authorization/#configuring-aws-iam

those docs are outdated, most stuff gets 404 since https://github.com/aws/aws-controllers-k8s was redirected to this repo?

those docs are outdated, most stuff gets 404 since https://github.com/aws/aws-controllers-k8s was redirected to this repo?

Thanks for the heads up @so0k! I'll correct those broken links ASAP.

This is done now.


Which tinyb version do you use?

Hello, I'm looking at this very interesting project because I'm using tinyb on my project too.
Could you tell me the tinyb vesion (or commit) in this repository?
Best regards,
HAKASHUN

Hi @HAKASHUN , it is the most recent one: b5e293bb3c11abc21327f5c18d79436fab167038. Thanks.

Thank you for your reply.
I've understand.

If you are interested in the project, I suggest you to have a look at these projects as well:
https://github.com/sputnikdev/bluetooth-manager
and
https://github.com/sputnikdev/bluetooth-cli
@HAKASHUN  ^^


Support executing missed tasks

Ex: I do a payment every hour. I shutdown the many-cron service for 3 hours. I want to be able to perform the 3 missing payments when I restart many-cron.

tokio-cron-scheduler v0.6-beta adds support for persistent storage. This will be useful for this task.
https://github.com/mvniekerk/tokio-cron-scheduler/releases/tag/0.6.0-beta.2


Adjust port number from 1431 to 1433

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

ID: f0c5d628-57bf-3b49-2b36-01a5ba4b6854
Version Independent ID: fade1a23-443a-1e5a-575b-73461b82775c
Content: Import process for large collections from Azure DevOps on-premises - Azure DevOps
Content Source: docs/migrate/migration-import-large-collections.md
Product: devops
Technology: devops-migrate
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@martins-vds  - Thank you for the correction. The article has been updated.


Component Exception: null is not an object

Hello,
I'm initializing the app using Expo bare workflow and followed the Getting Started guide. As soon as I started the app, I got this screen. Seems like the issue stems from ZendeskChat.init, and not ZendeskChat.startChat:

Main dependencies:
"expo": "~39.0.2",
"react-native": "~0.63.2",
"react-native-zendesk-chat": "^0.4.0"

Cocoapods version: 1.9.3
I'm unsure where to go from here. Any ideas?

Hi @binhxn! Have you ejected your expo or not?
react-native-zendesk-chat has native dependencies, so I believe you need to be ejected.
Unfortunately, we do not use expo, so you may need to use their forums to ask for expo specific advice.

Hi @fbartho I'm using Expo's Bare Workflow so it's essentially ejected from the Managed Workflow.
Hmm, I have a feeling it may be due to some other local dependency, but I'll continue digging around and reach out in the Expo forums, if needed. Feel free to close the issue!

The error message suggests the NativeModule might be missing, which is a pretty common issue for people working with expo
(I've seen reports of this relatively regularly, across multiple open source projects)

Any Luck? @binhxn

@shanusingh3 Not yet, I haven't had the time to revisit this issue =/


Update aws Community AMI to 0.29.2

Description
Hello,
Document duplication bug is very critical for us. It seems like you solved the issue in 0.29.2. We use aws community AMIs. Is it possible to update community AMI version from 0.29.1 to 0.29.2
Thanks.
Expected behavior
Latest version in AWS must be bug free.
Current behavior
0.29.1 has document duplication bug.
Screenshots or Logs
Environment (please complete the following information):

OS: [e.g. Debian GNU/Linux]
Browser: [e.g. Chrome version 90.0]
Meilisearch version: [e.g. v.0.29.1]
instant-meilisearch version: [e.g. v0.5.0]
instantsearch.js version: [e.g. v4.23.0]

I opened issue in MeiliSearch repository.


Cleanup after new data model

Description

Change from pointers to interface to just an interface for the recent data model split. Took the opportunity to clean up some of the related tests so they would be more correct (when setting env vars) / easier to follow (making TestNewDiscoveryMismatch not panic).
Why is this needed

I think #27 was merged prematurely. Lots of commented out code that should have been deleted, oddness in the pointer-to-interface and some hard to follow tests. This is me polishing some of that up.
Fixes: #
How Has This Been Tested?

go test ./...
How are existing users impacted? What migration steps/scripts do we need?

No anticipated impact.
Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[x] added unit or e2e tests
[ ] provided instructions on how to upgrade

As always, reviewing each commit one-at-a-time would make it easiest to review.

I've gone through every commit, and they all look good to me. Thanks for this. 👍


Add Face Registration Endpoint

Description
@Devasy23  This PR introduces a new Face Registration feature to the FaceRec project using FastAPI and DeepFace. It provides an endpoint that allows users to register their face, along with associated metadata (such as name), into the MongoDB database.
Key Features:

FastAPI Endpoint: /register/ accepts a form field (name) and an image file (image) for face registration.
DeepFace Integration: Extracts face embeddings using the Facenet model from DeepFace.
MongoDB Storage: Stores the face embeddings and metadata in the face_recognition database.
Error Handling: Includes error handling for failed face registration or database operations.

Usage Example:
To register a new face, send a POST request with the following form data:
POST /register/
Content-Type: multipart/form-data
Body:
  - image: (upload file)
  - name: "User's Name"

Hi @Sachin2815 - refer to "/create_new_faceEntry" endpoint. We already have this endpoint to allow users to register their face!

Hey @Sachin2815 ,
I think you can go over the code base first and check the issues. You can create a new issue if you have an idea or you can also contribute to existing issues which you find interesting.
Closing this pull request for now.


Added new apps :3

Salam :)
I added AllCast, Buzzfeed, Chromecast, Cnet, Fitbit, iShows, iTunesU, Marvis, Meerkat, MyFitnessPal, OnePassword, Periscope, Radium, Super Stickman Golf 2, Ted, and Whyd.
@Mazyod Just one small note:
Marvis fallbackURL shows this 👇🏼

But when I tapped continue or cancel I forgot what I tapped. Anyways, it works fine. So should I keep it or it's better to leave the fallbackURL empty?
إن شاء الله More Apps will be added ASAP :3

Thanks, about Marvis, you can simply change https to http. That should fix the warning.

@Mazyod Ok done I changed https to http and I add five more apps :3

@Maryom You also need to update the test :x: :grin:

@Mazyod I updated it 😁 Ok I will delete my frok and PR new one, do you think it will solve the  :x:

@Maryom just update the code and push a new commit, that's all

@Mazyod Ok I understood you Marvis test yup I didn't update it.

Thanks, this is looking great :star2:

@Mazyod Your welcome 😊 Thanks for all stars you wrote I like them 💯 I don't know where is our conversation about App setting so I will tell you here: this is what I found:
I just got a "rejected" from iTunes Connect this morning, for "prefs:root" is a private API ( there are apps using prefs:root on App Store
http://stackoverflow.com/questions/8246070/ios-launching-settings-restrictions-url-scheme

@Maryom Thanks, yes this confirms my doubts .. We shouldn't add it unless it's documented by Apple.

@Mazyod Ok deal :)