Issue: UnicodeDecodeError when running .txt files using TextLoader

Issue you'd like to raise.
Hello - I receive a UnicodeDecodeError when running the below code:
from dotenv import load_dotenv
load_dotenv()
from langchain.llms import OpenAI
from langchain.vectorstores import Chroma
from langchain.embeddings.openai import OpenAIEmbeddings
from langchain.text_splitter import CharacterTextSplitter
from langchain.chains import RetrievalQA
llm = OpenAI(temperature=0.1)
from langchain.document_loaders import TextLoader
loader = TextLoader("./Training/test2.txt")
documents = loader.load()
text_splitter = CharacterTextSplitter(chunk_size=1000, chunk_overlap=0)
texts = text_splitter.split_documents(documents)
embeddings = OpenAIEmbeddings()
docsearch = Chroma.from_documents(texts, embeddings)
qa = RetrievalQA.from_chain_type(llm=OpenAI(), chain_type="stuff", retriever=docsearch.as_retriever(search_kwargs={"k": 1}))
query = "How much did the judge fine Twitter?"
qa.run(query)
The test2.txt is a 1,600-word UTF-8 encoded file. Here is the error text that I receive:
Traceback (most recent call last):
File "C:\Users\Admin\PycharmProjects\pythonProject\Misc\Testing.py", line 17, in
documents = loader.load()
^^^^^^^^^^^^^
File "C:\Users\Admin\PycharmProjects\pythonProject\Misc\venv\Lib\site-packages\langchain\document_loaders\text.py", line 18, in load
text = f.read()
^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\encodings\cp1252.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 1079: character maps to
Any advice would be greatly appreciated.
Suggestion:
No response

This worked, thank you!

Hello,
I used encoding='cp1251' in TextLoader. Everything is ok when I see the result of loading. But when I execute
qa_chain = RetrievalQA.from_chain_type(llm, retriever=db.as_retriever())
I got the error: 'charmap' codec can't decode byte 0x81 in position 33: character maps to
I tried to convert source file into utf-8 encoding, but the error still the same. :-(
None of your recommendations doesn't work.


Helm-controller may leave resources after helm-release removal

{"level":"info","ts":"2024-07-24T13:57:17.294Z","msg":"uninstalled Helm release for deleted resource","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"ap-test","namespace":"hmc-system"},"namespace":"hmc-system","name":"ap-test","reconcileID":"e6d7f7e4-7c33-403f-98b3-a1f1b7da9aa9"}

k get secret | grep ap-test.v1
sh.helm.release.v1.ap-test.v1

I think with fix for #217 this issue will be fixed as well.

It is related to #217 and should be fixed with it


Mount configMap and secret by values object name

Details
Describe the solution you'd like:
I'd like to be able to mount ConfigMap in persistance section using it's name from configMaps section.
The best would be if secrets would also be supported here in the same way.

Additional Information:
This is already possible in envFrom section of controller, this is exactly what I'd like to see in persistance section.

That's a great idea, thanks! :) I've added it to the upcoming v3 version

Tests on the merge request failed ;D
Thank you for very fast response and the implementation!


Can't bind to 'mdDatepickerToggle' since it isn't a known property of 'button'.

Bug, feature request, or proposal:
[X] Bug
What is the expected behavior?
I am update with npm install --save angular/material2-builds angular/cdk-builds and my DatePicker not work, my browser terminal return error with mdDatepickerToggle
Can't bind to 'mdDatepickerToggle' since it isn't a known property of 'button'
<button mdSuffix [ERROR ->][mdDatepickerToggle]="pickerInit"></button>

This is my code
<md-input-container>
                  <input
                    mdInput
                    [mdDatepicker]="pickerInit"
                    placeholder="Fecha inicial"
                    [min]="minDate"
                    [max]="maxDate"
                    [value]="10-2-2017"
                    name="init"
                    #init="ngModel"
                    ngModel
                    required>
                  <button mdSuffix [mdDatepickerToggle]="pickerInit"></button>
                </md-input-container>
                <md-datepicker #pickerInit></md-datepicker>

5 minutes ago I worked well, I do not know what happened
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.0.0
Material github:angular/material2-builds (this show in package.json)
OS Mac

As of 5317, [mdDatepickerToggle] attribute has been changed to md-datepicker-toggle element

use can use md-datepicker-toggle like this:
 <md-datepicker-toggle mdSuffix [for]="picker"></md-datepicker-toggle>
Hope this will help you :)

@CaerusKaru I think there is a lot of example code out there with the former type <button mdSuffix [mdDatepickerToggle]="pickerInit"></button>
https://material.angular.io/components/datepicker/overview being one.

@BenRacicot Yes, because the current release (2.0.0-beta.8) still officially supports the old type. This is a breaking change before beta 9, and the documentation will be updated accordingly.

Thank you for clarifying @caeruskaru! Much clearer now. Looking forward to beta.9. I check everyday!

@CaerusKaru not sure if I should open a new ticket or not but is this implemented in beta.10?
Getting loads of errors with
<md-input-container style="width: 100%">
                <input mdInput formControlName="startDate" [mdDatepicker]="minDatePicker" placeholder="Min date">
                <!-- <button mdSuffix [mdDatepickerToggle]="minDatePicker"></button> -->
                <md-datepicker-toggle mdSuffix [for]="minDatePicker"></md-datepicker-toggle>
            </md-input-container>

What can I do to help here?

Guys any update regarding the usage of date-picker, on using <md-datepicker-toggle mdSuffix [for]="picker"> ; i get this error
ERROR TypeError: Cannot read property 'disabled' of undefined
at MdDatepickerToggle.get [as disabled] (material.es5.js:20168)
at Object.View_MdDatepickerToggle_0._co [as updateDirectives] (MdDatepickerToggle.html:1)
at Object.debugUpdateDirectives [as updateDirectives] (core.es5.js:13075)
at checkAndUpdateView (core.es5.js:12255)
at callViewAction (core.es5.js:12620)
at execComponentViewsAction (core.es5.js:12552)
at checkAndUpdateView (core.es5.js:12261)
at callViewAction (core.es5.js:12620)
at execEmbeddedViewsAction (core.es5.js:12578)
at checkAndUpdateView (core.es5.js:12256)

@ronit123321 Using the example here, adding the disabled property to md-datepicker-toggle works properly. If you're having this issue and can recreate it in a plunkr, please file a separate issue.

Returning to an Angular + Material project after a month 😂 🔫

I know your pain @elwinarens ! Look out for this too: https://github.com/angular/material2/pull/7346


Unable to see @ symbol

Using Version 15.117.27414.0
I created some tasks in TFS and assigned to my team members.
Team member could see it in his list and change status, update comments.
But the team member cannot see '@' for tagging. Because of this, I as a manager do not get mails on what he has updated.
What could be the reason that he cannot tag people in discussions ?
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@nitu1702 This channel is for Docs site related feedback. So I transferred your issue to Visual Studio team issue channel. They will help you there.


Observed instances of "object is not an instance of declaring class"

This crops up when calling JAX-RS resources after calling one of the post- or media-updating AtomPub resources, and so it's likely that the trouble cropped up with that conversion. It's not consistent... it's possible to call a normal GET resource fine, but then it becomes "infected" after calling a (failing) update resource.

This may be a fleeting or rare problem: trying to reproduce it now, I can't.


add option --skip-existing to not change checked out branch when no version is specified

When the version: field is left blank for git repositories, the GitClient.import_ function will currently use git remote show ... to find the name of the HEAD branch of the remote repository and then automatically check out that branch.
This is undesirable if vcstool is being used to clone/update the source directories in a workspace where the local version might want a different branch than the remote's HEAD. To get that behavior, this PR introduces an --ignore-head flag that will tell the GitClient.import_ function to not perform any checkout if no version is explicitly listed.
From glancing over the other clients, it looks like this new behavior will actually make the GitClient behave more similarly to the other clients. But since it's a potentially significant change in behavior, this PR introduces a new flag to explicitly enable this behavior, and vcs-import will continue to default to the old behavior.

I am not sure the behavior you describe is desired.
In general the idea is that a .repos file specifies a set of repositories with a specific branch/tag/hash. After an initial import of the file the file system should contain exactly the described state. An empty version means the default branch in this context (similar to the git command line interface). If you update existing working copies which might be in any arbitrary state the goal is that after running vcs import your file system is in the same state as it would be after an initial / fresh import.
In your use case that doesn't seem to be the case / desire. While the .repos file implicitly references the default branch you want the working copy to stay on an already checked out custom branch instead. I would consider this undesired behavior of the tool and therefore I am not sure if adding such an option is a good idea.
I don't know anything about your use case but why are the branch names in the .repos file and the local working copy different in the first place? Maybe a change in process would be an alternative.

After an initial import of the file the file system should contain exactly the described state.

When the state is not described (i.e. no version is specified), then what should be considered the exact described state?

An empty version means the default branch in this context

That's not currently the behavior for the mercurial client which simply won't check out any particular branch if no version is specified. The git client seems to be unique in this behavior.

If you update existing working copies which might be in any arbitrary state the goal is that after running vcs import your file system is in the same state as it would be after an initial / fresh import.

My hope is that we can allow developers (i.e. people writing the .repos files) to leave certain versions unspecified so that the working copy can be whatever the end users (i.e. people consuming the .repos files) currently have on their machine.
Conceptually I think this makes perfect sense, and I would have expected this to be the default behavior. If no version is specified, then I would expect that to imply "any version" (which defaults to HEAD when no version was already present locally) rather than "strictly the version that the upstream repo considers default".

I don't know anything about your use case

We have fast moving, complex project with a large team of internal and external collaborators where we need to introduce new packages on a regular basis. Rather than having everyone on the team manually clone new packages into their various workspaces whenever they need new things, we provide a tool that they can run to fetch any new packages that may have been introduced to the project.
At first we wrote custom machinery to automatically clone the repos and, when necessary, check out specific versions (because for some repos we do want specific versions while for other actively developed repos it's less important). But then we realized that we could just dump that effort and use vcstool instead. The .repos file format was especially nice for organizing and describing what repos were needed.
However, when it comes to the repos that are being actively developed by members of the team, it can be irritating if this tool is automatically changing the branches that they're actively working on. And if there are any uncommitted changes in one of those branches, then the tool errors out because the git checkout command will return a non-zero exit code.

but why are the branch names in the .repos file and the local working copy different in the first place?

For some repos the .repos file does not specify a branch name at all. Those versionless repo entries were meant to suggest that any version is to be accepted for that repo.

I am not sure the behavior you describe is desired.

I understand that the proposed behavior may be controversial and undesirable for some users, so that's why it's guarded by an optional command line flag. It needs to be explicitly turned on, or else the old behavior will continue to be the default.

When the state is not described (i.e. no version is specified), then what should be considered the exact described state?

Imo the same behavior as the git CLI is desired. If you git clone a repo you will checkout the default branch.

Rather than having everyone on the team manually clone new packages into their various workspaces whenever they need new things, we provide a tool that they can run to fetch any new packages that may have been introduced to the project.

How about adding an option to vcs import instead - something like --skip-existing - which simply won't touch directories which already exist? Such an options seems to much more closely describe your intended behavior.

How about adding an option to vcs import instead - something like --skip-existing - which simply won't touch directories which already exist?

This would suit my use case. Although I think the most sensible behavior is it should only skip existing directories if they match the specified URL, i.e. this check and this check should still be performed.
At that point I think the current PR is exactly what's being prescribed, except the argument --ignore-head would be changed to --skip-existing.

Although I think the most sensible behavior is it should only skip existing directories if they match the specified URL ...

I disagree on this. I don't see a different between a user switching to custom branch or a fork - in either of the two cases the new option should skip touching that existing working copy imo. Therefore the new option should skip any existing directory - independent of its state.

The idea would be to verify that the existing directory is actually a copy of the intended repo and not a random directory that the user created at some time. If it's some random other directory rather than the intended repo, then the tool would exit with an error.

Also note that the verification looks at whether the intended url is any one of the remotes for the repo, so the local copy can still be primarily aimed at a fork.

The idea would be to verify that the existing directory is truly a copy of the intended repo and not a random directory that the user created at some time. If it's some random other directory rather than the intended repo, then the tool would exit with an error.

Sounds good to me. Then my previous proposal sounds reasonable:

Therefore the new option should skip any existing directory - independent of its state.

Depending on the state of the existing directory the tool will either:

just skip it when the directory contains a working copy which at least has one remote with the specified URL or
return an error for that directory if all remotes are unrelated or the directory doesn't even contain a working copy at all

Either way the directory is not being modified (e.g. to a different remote / branch).
Would you be able to update the PR with the revised logic?

That sounds good to me. The only change that needs to be made to this PR then is renaming the --ignore-head flag to --skip-existing.
I'm traveling without a computer this weekend, but I'll see if GitHub's mobile UI can do the job.

I've attempted to make the changes with my phone, but I won't be able to test it until I have computer access.

It would be good to also add tests covering the discussed cases.

I've added tests for each of the conditions that have been discussed, and they seem to be passing.

Thanks for iterating on the patch.
I tried to integrate the new tests into the existing .repos file (to also cover the no-version entry in the other commands) and merge the tests into the existing function test_reimport since it semantically fits in there.
It took a few more iterations than I expected but the current state looks good. Can you please give it a try with the current patch and comment if it still works for your use case. Thanks.

Yep, this worked great, thanks!

FYI #136 to also skip non-git existing directories.


Add Fastlane support

Finally, it works... 😭
Still NOT Fixing #32 though, but at least we know what's going on... And this provides basic code for https://github.com/Life-USTC/Discussions/issues/2
One thing to notice that this actually breaks c83c62afc80b6e1440b1360958e7e45e5eee1a6c, and there's no way to add prefix like 3a7008df745b2198ee2c9a13fd7f57ef638befb9 to overcome this.
I'm ignoring all of these and first make TestFlight messages clear.


Tweak and sync description sections on all platforms

Just noticed these were a bit out of sync during my initial exploration of rim

Thanks!


Error: 0x80070005, bash doesn't run anymore

Your Windows build number: Microsoft Windows [Versión 10.0.15063]

What you're doing and what's happening:  When running bash from cmd or from shortcut icon, even when running as Admin.

What's wrong / what should be happening instead: I can't run bash anymore from anywhere.

Detail:

LxFs (HOME in Bash) was accessed and modified from Windows or programs running on Windows.

Answer from BashOnWindows team:

Editing LxFs from Windows is not supported.

Finally, it is very nice to have Bash in Windows, thank you!

Have you installed/changed any anti-virus/anti-malware software on your computer? Sounds similar to #852

Nope, I haven't. Windows defender is the only software of that kind running; I just disabled Real Time Protection in the Security Center and tried again to execute bash, but same error displayed.
I read the #852 and executed the trace cmd scripts, would it be useful to send the .etl files?

Yes those would be useful.

Here you go!
lxcore_trace.zip

Editing LxFs from Windows is not supported, IIRC.
In later versions, you won't be able to get to it at all because it's moved under %PROGRAMFILES%\WindowsApps, which is protected from even Administrators.

I'll reinstall WSL and forget about accessing LxFs from Windows.
Thank you for your time!

Uhm, 1. I don't speak on behalf of Microsoft...

In later versions, you install Ubuntu from Windows Store, then run ubuntu.exe (-c ifconfig, for example), not bash.exe anymore.

When this day comes i will just stick to Arch dual boot

@neojal - I took a look at your trace and it looks like something in your %localappdata%\lxss\temp directory cannot be deleted.  Can you try deleting that folder manually?

@benhillis - I fully uninstalled and then reinstalled WSL before your last comment, so Bash is working again. However, I'll follow the previous workflow and let you know if the error rises again and I'll keep in mind about the temp directory. Thank you!

@neojal Thanks for reporting this and sharing logs.
in case you've not seen it, we strongly recommend against spelunking into the Linux filesystem from Windows or using Windows apps: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-not-change-linux-files-using-windows-apps-and-tools/
We are working to improve this scenario in the future, but for now the guidance remains: Avoid spelunking until further notice ;)
Closing for now. Feel free to reopen if you see this issue reoccur.


#20139 fix PG and forks routines header creation - add default value …

fix PG and forks routines header creation - add a default value for parameters;
add a new enum argument for Greenplum.
https://docs.vmware.com/en/VMware-Greenplum/7/greenplum-database/ref_guide-sql_commands-CREATE_FUNCTION.html
https://docs.vmware.com/en/VMware-Greenplum/6/greenplum-database/ref_guide-system_catalogs-pg_proc.html (new enum i)
Please check the following:

[x] DEFAULT value added only for procedures/functions DDL in PG
[x] DEFAULT value added only for procedures/functions DDL in Greenplum
[x] You can rename function via UI (parameter name still working without default)
[x] You can drop function via UI (parameter name still working without default)

verified


⚠ DesiTorrents has degraded performance

In a7deae4, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 6693 ms

Resolved: DesiTorrents performance has improved in 5421af1 after 9 minutes.


Horizon node goes down after a few hours with invalid memory address or nil pointer.

I installed Stellar-Core and Stellar-Horizon using the Debian binary package format on Ubuntu LTS. I set up a private network with 5 Stellar-Core nodes. After ensuring that all Stellar-Core nodes were synchronized, I proceeded to configure and launch a Stellar-Horizon node. However, I encountered an error message stating 'Still Ingesting.' Upon investigation, I found that the Stellar-Captive-Core was not syncing and remained in a 'catching up' state. Furthermore, I am experiencing an issue where the server frequently goes down after a few hours with a invalid memory address or nil pointer
The output of the command stellar-horizon version is:
2.31.0-d1d911f6ed7396fd705d8f2068f70f468012102e
go1.22.4

The output of the command stellar-core version is:
Warning: running non-release version stellar-core 21.1.0 (b3aeb14cc798f6d11deb2be913041be916f3b0cc) of stellar-core
stellar-core 21.1.0 (b3aeb14cc798f6d11deb2be913041be916f3b0cc)
ledger protocol version: 21
rust version: rustc 1.74.1 (a28077b28 2023-12-04)

Horizon node standard output:
ERRO[2024-07-02T17:27:56.696+03:30] History: Could not download file: archive node03 maybe missing file history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:27:56.696+03:30] History: Missing HAS for ledger 7: maybe stale archive node03  pid=131852 service=ingest subservice=stellar-core
INFO[2024-07-02T17:27:58.696+03:30] History: Downloading history archive state: history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
WARN[2024-07-02T17:27:58.721+03:30] Process: process 131953 exited 22: curl -sf http://NODE01_IP/history/00/00/00/history-00000007.json -o buckets/tmp/history-a708a75f7c0058c1/a78c94a842ed0588-stellar-history.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:27:58.722+03:30] History: Could not download file: archive node02 maybe missing file history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:27:58.722+03:30] History: Missing HAS for ledger 7: maybe stale archive node02  pid=131852 service=ingest subservice=stellar-core
INFO[2024-07-02T17:28:02.722+03:30] History: Downloading history archive state: history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
WARN[2024-07-02T17:28:02.745+03:30] Process: process 131954 exited 22: curl -sf http://NODE05_IP/history/00/00/00/history-00000007.json -o buckets/tmp/history-a708a75f7c0058c1/a78c94a842ed0588-stellar-history.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:02.746+03:30] History: Could not download file: archive node05 maybe missing file history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:02.746+03:30] History: Missing HAS for ledger 7: maybe stale archive node05  pid=131852 service=ingest subservice=stellar-core
INFO[2024-07-02T17:28:08.746+03:30] History: Downloading history archive state: history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
WARN[2024-07-02T17:28:08.769+03:30] Process: process 131956 exited 22: curl -sf http://NODE05_IP/history/00/00/00/history-00000007.json -o buckets/tmp/history-a708a75f7c0058c1/a78c94a842ed0588-stellar-history.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:08.770+03:30] History: Could not download file: archive node05 maybe missing file history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:08.770+03:30] History: Missing HAS for ledger 7: maybe stale archive node05  pid=131852 service=ingest subservice=stellar-core
INFO[2024-07-02T17:28:20.770+03:30] History: Downloading history archive state: history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
WARN[2024-07-02T17:28:20.794+03:30] Process: process 131958 exited 22: curl -sf http://localhost/history/00/00/00/history-00000007.json -o buckets/tmp/history-a708a75f7c0058c1/a78c94a842ed0588-stellar-history.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:20.794+03:30] History: Could not download file: archive node01 maybe missing file history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:20.794+03:30] History: Missing HAS for ledger 7: maybe stale archive node01  pid=131852 service=ingest subservice=stellar-core
INFO[2024-07-02T17:28:25.593+03:30] default: Performing maintenance               pid=131852 service=ingest subservice=stellar-core
INFO[2024-07-02T17:28:25.593+03:30] History: Trimming history <= ledger 0 (rmin=4294967295, qmin=1, lmin=0)  pid=131852 service=ingest subservice=stellar-core
INFO[2024-07-02T17:28:40.794+03:30] History: Downloading history archive state: history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
WARN[2024-07-02T17:28:40.818+03:30] Process: process 131960 exited 22: curl -sf http://localhost/history/00/00/00/history-00000007.json -o buckets/tmp/history-a708a75f7c0058c1/a78c94a842ed0588-stellar-history.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:40.818+03:30] History: Could not download file: archive node01 maybe missing file history/00/00/00/history-00000007.json  pid=131852 service=ingest subservice=stellar-core
ERRO[2024-07-02T17:28:40.818+03:30] History: Missing HAS for ledger 7: maybe stale archive node01  pid=131852 service=ingest subservice=stellar-core
 Close of ledger 28493 buffered.
 panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x10f8024]

goroutine 117 [running]:
github.com/stellar/go/ingest/ledgerbackend.(*bufferedLedgerMetaReader).getChannel(...)
        github.com/stellar/go/ingest/ledgerbackend/buffered_meta_pipe_reader.go:108
github.com/stellar/go/ingest/ledgerbackend.(*stellarCoreRunner).getMetaPipe(0xc0000c2500?)
        github.com/stellar/go/ingest/ledgerbackend/stellar_core_runner.go:554 +0x4
github.com/stellar/go/ingest/ledgerbackend.(*CaptiveStellarCore).GetLedger(0xc000227200, {0x1c7b810, 0xc00023aaf0}, 0x3e3f)
        github.com/stellar/go/ingest/ledgerbackend/captive_core_backend.go:655 +0x691
github.com/stellar/go/ingest/ledgerbackend.metricsLedgerBackend.GetLedger({{0x1c7e260?, 0xc000227200?}, {0x1c7e460?, 0xc0004937a0?}}, {0x1c7b810, 0xc00023aaf0}, 0x3e3f)
        github.com/stellar/go/ingest/ledgerbackend/metrics.go:38 +0x9b
github.com/stellar/go/services/horizon/internal/ingest.buildState.run({0x117c824?, 0x0?, 0x0?}, 0xc0005d2c88)
        github.com/stellar/go/services/horizon/internal/ingest/fsm.go:319 +0x337
github.com/stellar/go/services/horizon/internal/ingest.(*system).runStateMachine(0xc0005d2c88, {0x1c792c0, 0x26ed5a0})
        github.com/stellar/go/services/horizon/internal/ingest/main.go:665 +0x3c5
github.com/stellar/go/services/horizon/internal/ingest.(*system).Run(0xc0005d2c88)
        github.com/stellar/go/services/horizon/internal/ingest/main.go:539 +0x3a
github.com/stellar/go/services/horizon/internal.(*App).Serve.func1()
        github.com/stellar/go/services/horizon/internal/app.go:103 +0x2f
created by github.com/stellar/go/services/horizon/internal.(*App).Serve in goroutine 1
        github.com/stellar/go/services/horizon/internal/app.go:102 +0x285

The output of the command cat /etc/stellar/stellar-core.cfg is:
HTTP_PORT=11626
PEER_PORT=11625
PUBLIC_HTTP_PORT=false
RUN_STANDALONE=false
NETWORK_PASSPHRASE="My Private Network ; Feb 2024"
NODE_SEED="PRIVATE_KEY self"
NODE_IS_VALIDATOR=true
DATABASE="postgresql://dbname=core_database_name user=username password=password host=localhost"
DEPRECATED_SQL_LEDGER_STATE=false
LOG_FILE_PATH="/var/log/stellar/stellar-core-{datetime:%Y-%m-%d}.log"
BUCKET_DIR_PATH="/var/lib/stellar/buckets"
COMMANDS=["ll?level=debug"]
FAILURE_SAFETY=1
UNSAFE_QUORUM=false
CATCHUP_COMPLETE=false

NODE_HOME_DOMAIN="my.domain"
[[HOME_DOMAINS]]
HOME_DOMAIN="my.domain"
QUALITY="HIGH"

# [[VALIDATORS]]
# NAME="node01"
# HOME_DOMAIN="my.domain"
# PUBLIC_KEY="GB..."
# ADDRESS="NODE01_IP:11625"
# HISTORY="curl -sf http://NODE01_IP/{0} -o {1}"

[[VALIDATORS]]
NAME="node02"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GB..."
ADDRESS="NODE02_IP:11625"
HISTORY="curl -sf http://NODE02_IP/{0} -o {1}"

[[VALIDATORS]]
NAME="node03"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GB..."
ADDRESS="NODE03_IP:11625"
HISTORY="curl -sf http://NODE03_IP/{0} -o {1}"

[[VALIDATORS]]
NAME="node04"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GB..."
ADDRESS="NODE04_IP:11625"
HISTORY="curl -sf http://NODE04_IP/{0} -o {1}"

[[VALIDATORS]]
NAME="node05"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GD..."
ADDRESS="NODE05_IP:11625"
HISTORY="curl -sf http://NODE05_IP/{0} -o {1}"

[HISTORY.local]
get="cp /var/lib/stellar/history/vs/{0} {1}"
put="cp {0} /var/lib/stellar/history/vs/{1}"
mkdir="mkdir -p /var/lib/stellar/history/vs/{0}"

The output of the command stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'info' is:
Warning: running non-release version stellar-core 21.1.0 (b3aeb14cc798f6d11deb2be913041be916f3b0cc) of stellar-core
2024-07-01T20:59:17.170 [default INFO] Config from /etc/stellar/stellar-core.cfg
2024-07-01T20:59:17.174 [default INFO] Generated QUORUM_SET: {
   "t" : 3,
   "v" : [ "self", "node03", "node02", "node04", "node05" ]
}
{
   "info" : {
      "build" : "stellar-core 21.1.0 (b3aeb14cc798f6d11deb2be913041be916f3b0cc)",
      "ledger" : {
         "age" : 3,
         "baseFee" : 100,
         "baseReserve" : 100000000,
         "closeTime" :<PHONE_NUMBER>,
         "hash" : "6c8da53d06814966acd472d421e87f77bff9b96d4a46fc56114848b8aab03e80",
         "maxTxSetSize" : 100,
         "num" : 3360,
         "version" : 0
      },
      "network" : "My Private Network ; Feb 2024",
      "peers" : {
         "authenticated_count" : 4,
         "pending_count" : 0
      },
      "protocol_version" : 21,
      "quorum" : {
         "node" : "self",
         "qset" : {
            "agree" : 5,
            "cost" : 17776,
            "delayed" : 0,
            "disagree" : 0,
            "fail_at" : 3,
            "hash" : "04828e",
            "lag_ms" : 30,
            "ledger" : 3359,
            "missing" : 0,
            "phase" : "EXTERNALIZE",
            "validated" : true
         },
         "transitive" : {
            "critical" : null,
            "intersection" : true,
            "last_check_ledger" : 1521,
            "node_count" : 5
         }
      },
      "startedOn" : "2024-07-01T14:51:13Z",
      "state" : "Synced!"
   }
}

The output of the command stellar-core --conf /etc/stellar/stellar-captive-core.cfg http-command 'info' is:
Warning: running non-release version stellar-core 21.1.0 (b3aeb14cc798f6d11deb2be913041be916f3b0cc) of stellar-core
2024-07-07T06:07:43.934 [default INFO] Config from /etc/stellar/stellar-captive-core.cfg
2024-07-07T06:07:43.935 [default INFO] Generated QUORUM_SET: {
   "t" : 3,
   "v" : [ "node01", "node03", "node02", "node04", "node05" ]
}

Content-Length: 1287
Content-Type: application/json

{
   "info" : {
      "build" : "stellar-core 21.1.0 (b3aeb14cc798f6d11deb2be913041be916f3b0cc)",
      "ledger" : {
         "age" : 0,
         "baseFee" : 100,
         "baseReserve" : 100000000,
         "closeTime" : 0,
         "hash" : "8401376de9f86caa0934e10ce5fbc8706d1a72f4db6b0243601e640fed00dd44",
         "maxTxSetSize" : 100,
         "num" : 1,
         "version" : 0
      },
      "network" : "My Private Network ; Feb 2024",
      "peers" : {
         "authenticated_count" : 3,
         "pending_count" : 0
      },
      "protocol_version" : 21,
      "quorum" : {
         "node" : "GCAPG",
         "qset" : {
            "agree" : 5,
            "cost" : 21692,
            "delayed" : 0,
            "disagree" : 0,
            "fail_at" : 3,
            "hash" : "04828e",
            "lag_ms" : 29,
            "ledger" : 60022,
            "missing" : 0,
            "phase" : "EXTERNALIZE"
         },
         "transitive" : {
            "critical" : null,
            "intersection" : true,
            "last_check_ledger" : 59955,
            "node_count" : 6
         }
      },
      "startedOn" : "2024-07-07T02:32:45Z",
      "state" : "Catching up",
      "status" : [ "Catching up to ledger 59903: downloading ledger files 1/1 (100%)" ]
   }

The output of the command cat /etc/default/stellar-horizon is:
NETWORK_PASSPHRASE="My Private Network ; Feb 2024"
LOG_FILE_PATH="/var/log/stellar/stellar-horizon-{datetime:%Y-%m-%d}.log"
DATABASE_URL="postgres://username:password@localhost/horizon_database_name"
CAPTIVE_CORE_CONFIG_PATH="/etc/stellar/stellar-captive-core.cfg"
STELLAR_CORE_URL="http://<IP_ADDRESS>:11626"
STELLAR_CORE_BINARY_PATH=/usr/bin/stellar-core
HISTORY_ARCHIVE_URLS="http://NODE01_IP/,http://NODE02_IP/,http://NODE03_IP/,http://NODE04_IP/,http://NODE05_IP/"
HISTORY_RETENTION_COUNT=518
LOG_LEVEL="info"
CAPTIVE_CORE_STORAGE_PATH="/var/lib/stellar"
ENABLE_CAPTIVE_CORE_INGESTION="true"
CAPTIVE_CORE_USE_DB=true
STELLAR_CAPTIVE_CORE_HTTP_PORT=0
PER_HOUR_RATE_LIMIT="72000"
DISABLE_ASSET_STATS="true"
CHECKPOINT_FREQUENCY=8
ADMIN_PORT=6060
PORT=8000
PER_HOUR_RATE_LIMIT=9000
INGEST=true
FRIENDBOT_URL=http://localhost:8004/

The output of the command cat /etc/stellar/stellar-captive-core.cfg is:
HTTP_PORT=11726
PEER_PORT=11725
PUBLIC_HTTP_PORT=false
RUN_STANDALONE=true
NETWORK_PASSPHRASE="My Private Network ; Feb 2024"
DATABASE="sqlite3://stellar_core_captive.db"
LOG_FILE_PATH="/var/log/stellar/stellar-captive-core-{datetime:%Y-%m-%d}.log"
ARTIFICIALLY_ACCELERATE_TIME_FOR_TESTING=true
FAILURE_SAFETY=0
UNSAFE_QUORUM=true

[[HOME_DOMAINS]]
HOME_DOMAIN="my.domain"
QUALITY="HIGH"

[[VALIDATORS]]
NAME="node01"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GB..."
ADDRESS="localhost:11625"
HISTORY="curl -sf http://localhost/{0} -o {1}"

[[VALIDATORS]]
NAME="node02"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GB..."
ADDRESS="NODE02_IP:11625"
HISTORY="curl -sf http://NODE02_IP/{0} -o {1}"

[[VALIDATORS]]
NAME="node03"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GB..."
ADDRESS="NODE03_IP:11625"
HISTORY="curl -sf http://NODE03_IP/{0} -o {1}"

[[VALIDATORS]]
NAME="node04"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GB..."
ADDRESS="NODE04_IP:11625"
HISTORY="curl -sf http://NODE04_IP/{0} -o {1}"

[[VALIDATORS]]
NAME="node05"
HOME_DOMAIN="my.domain"
PUBLIC_KEY="GD..."
ADDRESS="NODE05_IP:11625"
HISTORY="curl -sf http://NODE05_IP/{0} -o {1}"

The output of the command free -h is:
               total        used        free      shared  buff/cache   available
Mem:           1.9Gi       476Mi        63Mi        89Mi       1.4Gi       1.1Gi
Swap:           11Gi        41Mi        11Gi

This issue has been preview on the Pull Requests. To resolve,
Contact the dAppNode page to initiate a chat with the live agent on the chat button to get more information about your request via dAppNode


 A part of my testing efforts I also received a D6T-44L-06 sensor and set it up on my Raspberry Pi. I ran the unmodified version of your example script, unfortunately this time around I'm receiving output like this:
Thermal Sensor Temperature: 6553.5
1: 6553.5
2: 6553.5
3: 6553.5
4: 6553.5
5: 6553.5
6: 6553.5
7: 6553.5
8: 6553.5
9: 6553.5
10: 6553.5
11: 6553.5
12: 3276.7
13: 3263.9
14: 3263.9
15: 3263.9
16: 3263.9
pec: 0x7f
Thermal Sensor Temperature: 6553.5
1: 6553.5
2: 6553.5
3: 6553.5
4: 6553.5
5: 6553.5
6: 6553.5
7: 6553.5
8: 6553.5
9: 6553.5
10: 6553.5
11: 6553.5
12: 6553.5
13: 6553.5
14: 6553.5
15: 6553.5
16: 6553.5
pec: 0xff

Do you have any idea what the issue could be?

Hey,
My original attempt for this sensor was on a Raspberry Pi. I believe the Omron sensors requires a repeated start (it shows it in their app note, and I was unable to get it working without the repeated start) to properly read the data. After a bit of digging through forums and datasheets, I found that the raspberry pi i2c hardware does not support repeated starts.
Here is a link to one of the forums:
https://www.raspberrypi.org/forums/viewtopic.php?t=15840
After struggling for a few days with the Raspberry Pi, I picked up a beaglebone I had laying around, and the same code worked. I looked through a protocol analyzer, and the only difference between the 2 was the repeated start, so it seems like the raspberry pi just isn't the right hardware for interfacing with this device. 2 possibilities I see for getting this working on the RPI:

Bitbang i2c
Read sensor data from MCU like Arduino and pass that data along to the RPI over Serial, SPI, I2C, etc.

Should anyone stumble upon this issue in the future, I actually found a way to make the d6t sensors work with the Raspberry Pi. I used the i2c-bus library from npm for this. You can find my code as reference here: https://github.com/mKeRix/room-assistant/blob/thesis/services/d6t.service.js
The code in that branch is experimental, so excuse the mess. Generally this seems to be quite reliable, however I do get some wrong data sometimes. To counter this the PEC check should be implemented as well. I based my code on the D6T whitepaper.


C API function signatures should communicate object ownership, so caller knows what they need to free

@vsbogd wrote:

I would also keep this information in a function signature not only in comments because the signature of function has better visibility from my perspective. One way is to use specific names of functions and variables which notifies about ownership rules. For example "_ptr" postfix could mean this is a shared pointer and not a moved object. Name without a postfix means the object is moved. Please see the examples below:

// _self is moved out (consumed), other_ptr is borrowed, return value is created
struct bindings_set_t *bindings_merge_v2(struct bindings_t *_self, const struct bindings_t *other_ptr);

// set_ptr is borrowed, bindings is moved out (consumed)
void bindings_set_push(struct bindings_set_t *set_ptr, struct bindings_t *bindings);

// vec_ptr is borrowed, idx is moved out (consumed), return value is created
const struct atom_t *vec_atom_get_ptr(const struct vec_atom_t *vec_ptr, uintptr_t idx);

As described above could establish a naming convention.  Alternatively, we could use a pass-by-reference vs. pass-by-value convention.  See https://github.com/trueagi-io/hyperon-experimental/issues/350

Alternatively, we could use a pass-by-reference vs. pass-by-value convention.

Could you please elaborate your idea, I don't clearly understand what exactly do you suggest.

My thinking is that objects passed by value would be consumed, whereas objects passed by reference would simply be borrowed.  So it "feels" like Rust although there is no borrow checker to keep you honest.
For example:
// _self is moved out (consumed), other is borrowed, return value is created
struct bindings_set_t bindings_merge_v2(struct bindings_t _self, const struct bindings_t *other);

This convention would require https://github.com/trueagi-io/hyperon-experimental/issues/350 to be fully implemented.  Although there are good reasons to do that regardless of the ownership convention we settle on.

This has been fully implemented with https://github.com/trueagi-io/hyperon-experimental/pull/395.  Closing.


Phone number have been banned shortly after entering authentication code

Hi!
I have just compilied TDLib with CSharp sample console application. Shortly after I had entered phone number and authorization code my phone number was banned. Now while I am trying to sign in, I just receive code = 400, message = "PHONE_NUMBER_BANNED"
It's quite strange because official sample doesn't work with official library

I have the same problem.

i have banned two mobile phone numbers thanks to td_example. spent the whole day trying to figure it out... fed up

To be honest, the support responded quickly (within 12 hours) and unbanned my phone number. After that, I resorted to the Telethon library (in Python) - it's easier to use, doesn't require compiling and doesn't get your phone number banned. :)

telegram accounts randomly getting banned the admin itself either dont know the exact reason for ban or dont want to disclose to the user.
but i appreciate them,they unban accounts upon user request.

I'm confused with that. I did registration routine with tdlib and new number, sent getMe request and stop app. I run app second time and I got ban error. There is no ban behavior. It demotivates.

The only way to stop spam is to make it unprofitable. If spam account has been allowed to do "ban behavior", then it is too late to ban him, because it has already been justified. I've never heard about complaints about ban from ordinary users, so it seems that the system works good enough.

In my opinion, it's the implementation of the library that causes the problem. I don't see similar complaints from users of other Telegram libraries.

I'm using TDLib in production since february and none of my users got banned while using my app.
I think that the same applies to Telegram X.

i try use iGram app for windows and all my accounts blocked(

@konstantin24121 Please write phone numbers and other details to<EMAIL_ADDRESS>

same problem!
this problem occurs after TDlib1.3.0!
there isn't any way to fix it?

@StagsGit You need to write phone number and other details to<EMAIL_ADDRESS>

@levlam I found the solution
just use API_ID and API_HASH that got from an account that account ID begging with 7******** or under that
ban will not occurred :)

Faced the same issue trying to build and run TELEports for Ubuntu Touch. It's weird.

is it possible that we can back a banned phone number's data back ? this is so fkd up, i need my data!

@iMat1n If you believe that your account was blocked accidentally, you need to write its phone number and other details to<EMAIL_ADDRESS>

@iMat1n If you believe that your account was blocked accidentally, you need to write its phone number and other details to<EMAIL_ADDRESS>
i already did, im asking if its possible that i ca get my data back. they were my everything tbh!

Looks like there was a huge ban wave right now. Got my main account and sub account banned. Used telethon python library to play a game in one of channels.

@iMat1n If you believe that your account was blocked accidentally, you need to write its phone number and other details to<EMAIL_ADDRESS>
My two numbers got banned within 24hrs for no reason. I have written to the email but wondering how long it takes to have it resolved or have a response at least.

@luizrosevelt In my case it was ~ 12 hours.

@luizrosevelt In my case it was ~ 12 hours.

Thanks for the response. Seems telegram just blocks numbers randomly without reason.. sad

@luizrosevelt In my case it was ~ 12 hours.

Thanks for the response. Seems telegram just blocks numbers randomly without reason.. sad

it has to be some reasons because i've never got a ban on my sim card number and a voip number , but they both got banned after a few secounds that i logged in using my bot. it has to be some permissions i think to be granted to your account then u wont get a ban.
not 100% accturate but this is what i think.

My phone number was blocked this morning. I have no idea why? What do I do? I have important stuff going on there, I feel like crying o!

@spiffytwin Please, write to<EMAIL_ADDRESS>your phone number and description of the problem.

I have written to<EMAIL_ADDRESS>they are yet to reply. Please help
me out. The phone number is<PHONE_NUMBER>2. I was involved with some telegram
bots, maybe that's the reason for the ban.
On Mon, Oct 12, 2020, 7:33 PM Aliaksei Levin<EMAIL_ADDRESS>wrote:

@spiffytwin https://github.com/spiffytwin Please, write to
<EMAIL_ADDRESS>your phone number and description of the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tdlib/td/issues/312#issuecomment-707280947, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARLEBFWA2BZUMTCANWGPMVDSKNDWLANCNFSM4FKLDU6A
.

This just happened to me, more than 3 years after this issue was opened, it seems unbelievable that if this is a "bug" and is on such a big scale (it literally bans your account without any warning or questions) it has not been fixed for over 3 years and still does happen, I wrote to<EMAIL_ADDRESS>and waiting for an answer... Anyways thanks everyone here in this thread for helping others and explaining what to do, why it happened and saying it worked for you, I would have already lost my mind if I did not find this issue, lets just hope they will be able to recover my account and I won't lose any data, my contacts already see my account as "Deleted Account" :/

This just happened to me, more than 3 years after this issue was opened, it seems unbelievable that if this is a "bug" and is on such a big scale (it literally bans your account without any warning or questions) it has not been fixed for over 3 years and still does happen, I wrote to<EMAIL_ADDRESS>and waiting for an answer... Anyways thanks everyone here in this thread for helping others and explaining what to do, why it happened and saying it worked for you, I would have already lost my mind if I did not find this issue, lets just hope they will be able to recover my account and I won't lose any data, my contacts already see my account as "Deleted Account" :/

Don't worry, they usually resound max 2 days, which happened to me, use an alt account for now and you will have your accounts back as i got mine.
Literally every singe message was recovered, but chats were unmuted and pinned chats were lost their place as a pinned chat.
And about this problem, i don't think this is a "bug", it's more like Telegram is now more sensitive to some numbers and logins which happen not using the official clients.
Anyway, gl with getting your account back.

My phone number got unbanned but I still can't log-in, because when I try to, they refuse to send me an SMS like they used to, but they want me to enter a code that I was supposed to recieve on a different session, but ALL of my sessions got disconnected (also RIP secret chats...) so I can't do anything, if I try it on an older desktop client, they never send me any SMS, on the newest one it shows this screenshot below: and on my phone clients it literally wants to open my mail app???? so I am "softlocked"/stuck till they fix yet another stupid error... Does anyone have ANY idea what can I do? Like disconnecting all of my sessions from a website if thats possible? Or forcing them to send me an SMS somehow?

have you tried to login via mobile apps ?

@iMat1n If you believe that your account was blocked accidentally, you need to write its phone number and other details to<EMAIL_ADDRESS>
My two numbers got banned within 24hrs for no reason. I have written to the email but wondering how long it takes to have it resolved or have a response at least.

Yes same problem to me but i didnt unban why? I spent 6 hours but not unban

This just happened to me, more than 3 years after this issue was opened, it seems unbelievable that if this is a "bug" and is on such a big scale (it literally bans your account without any warning or questions) it has not been fixed for over 3 years and still does happen, I wrote to<EMAIL_ADDRESS>and waiting for an answer... Anyways thanks everyone here in this thread for helping others and explaining what to do, why it happened and saying it worked for you, I would have already lost my mind if I did not find this issue, lets just hope they will be able to recover my account and I won't lose any data, my contacts already see my account as "Deleted Account" :/

Don't worry, they usually resound max 2 days, which happened to me, use an alt account for now and you will have your accounts back as i got mine.
Literally every singe message was recovered, but chats were unmuted and pinned chats were lost their place as a pinned chat.
And about this problem, i don't think this is a "bug", it's more like Telegram is now more sensitive to some numbers and logins which happen not using the official clients.
Anyway, gl with getting your account back.

Can i get account unbanned?

I

This just happened to me, more than 3 years after this issue was opened, it seems unbelievable that if this is a "bug" and is on such a big scale (it literally bans your account without any warning or questions) it has not been fixed for over 3 years and still does happen, I wrote to<EMAIL_ADDRESS>and waiting for an answer... Anyways thanks everyone here in this thread for helping others and explaining what to do, why it happened and saying it worked for you, I would have already lost my mind if I did not find this issue, lets just hope they will be able to recover my account and I won't lose any data, my contacts already see my account as "Deleted Account" :/

Don't worry, they usually resound max 2 days, which happened to me, use an alt account for now and you will have your accounts back as i got mine.
Literally every singe message was recovered, but chats were unmuted and pinned chats were lost their place as a pinned chat.
And about this problem, i don't think this is a "bug", it's more like Telegram is now more sensitive to some numbers and logins which happen not using the official clients.
Anyway, gl with getting your account back.

I spent more than 6 hours
But no reply and unban
How to make unban bro

This just happened to me, more than 3 years after this issue was opened, it seems unbelievable that if this is a "bug" and is on such a big scale (it literally bans your account without any warning or questions) it has not been fixed for over 3 years and still does happen, I wrote to<EMAIL_ADDRESS>and waiting for an answer... Anyways thanks everyone here in this thread for helping others and explaining what to do, why it happened and saying it worked for you, I would have already lost my mind if I did not find this issue, lets just hope they will be able to recover my account and I won't lose any data, my contacts already see my account as "Deleted Account" :/

Don't worry, they usually resound max 2 days, which happened to me, use an alt account for now and you will have your accounts back as i got mine.
Literally every singe message was recovered, but chats were unmuted and pinned chats were lost their place as a pinned chat.
And about this problem, i don't think this is a "bug", it's more like Telegram is now more sensitive to some numbers and logins which happen not using the official clients.
Anyway, gl with getting your account back.

I mail them with when my account was banned there is help button and i report my issue and they didnt reply me i spent 9 hours bt didnt get reply and unban

My account got banned while playing with telega.el (a Telegram client built on TDLib) on the previous Saturday (almost a week now) and even after multiple mails to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I have not got a single reply from them.

@LordRishav Could you send banned phone number to https://t.me/tdlib_bot?

@levlam My account was unbanned. Thank you :)

A few days ago I used 64gram (an unofficial Telegram client) to register an account, because an official desktop client refused to request verification SMS. Right after registration was successfully completed, my number got banned. I filed a report via support section of Telegram website, they didn't respond via e-mail, but it seems ban was removed silently. Now, should I try to login via 64gram again, or it will lead to another ban?

My account was banned after I entered the verification code, I want to sync messages into Wechat because the Chinese policy makes it difficult for me to log into telegram,It's very difficult,  I'm not sending ads and I'm using my own phone, It's crazy.

Please how can I unban my telegram number and what are the details i should mail them to get my number unban?

@scrtsct You need to try to log in from an official mobile app and send a email to recover the account by following instructions provided by the app.

Mine has been a month or so and still banned

Please anyone with an updated info about how to get unbanned, I will appreciate. I have written to to team countless times with no reply from them and it's been 2months now

The support seems dead. They don't answer any emails or support tickets.

I'm trying to use my mobile phone number:<PHONE_NUMBER>08
But Telegram says it's banned. Please help.
App version: 11.0.0 (51439)
OS version: SDK 34
Device Name: Xiaomi22101316G
Locale: en

Please+959423501808
But
Telegram says it's banned. Please help. Please
check help my account. I have done nothing wrong to be banned I will appreciate if you unbun my account thanks you so much

I'm trying to use my mobile phone number:<PHONE_NUMBER>08
But Telegram says it's banned. Please help.
App version: 11.0.0 (51439)
OS version: SDK 34
Device Name: Xiaomi22101316G
Locale: en


No update in MQTT Binary Sensor #7478

Description:
This is a fix for issue #7478 where mqtt subscriptions containing special characters stopped working after PR #7269
Related issue (if applicable): fixes #7478
Pull request in home-assistant.github.io with documentation (if applicable): N/A
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Cherry-picked for 0.47


Unable to run ImageEmbedder

I use the example code to run the ImageEmbedder but it throws the following error,

anaconda3/envs/pose/lib/python3.8/site-packages/pycocotools/mask.py", line 3, in <module>
    import pycocotools._mask as _mask
  File "pycocotools/_mask.pyx", line 1, in init pycocotools._mask
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject

@Zumbalamambo Seems like pycocotools issue, and not related to ImageEmbedder. Could you please details about your working Environment?


Update to latest deps and improve API support for extra script data

This is not entirely resolved yet since we may decide that the extra script data should always be associated with tx outputs, in which case we'll want to adjust the API and CLI accordingly. So the CLI support is not yet included, pending that decision.

bors merge


feat(response): add assertSee

Hey 👋
This method can be useful when you don't want to run the browser but still want to assert that the response contains something.
Example:
test('a user can browse threads', async ({ assert, client }) => {
  const thread = await Factory.model('App/Models/Thread').create(1)
  const response = await client.get('/threads').end()

  response.assertStatus(200)
  response.assertSee(thread.title)
})

I believe assertTextHas is more clear on what exactly the assertion is about

Updated 👍

Thanks 😄


User can create pod run as root in K8s cluster v1.13.4 that enabled PSP RunAsNonRoot

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
A k8s v1.13.4 cluster with enabled PSP via Rancher UI.

PSP that aims to prevent running pods as root user:

apiVersion: extensions/v1beta1
kind: PodSecurityPolicy
metadata:
  annotations:
    serviceaccount.cluster.cattle.io/pod-security: tcloud
    serviceaccount.cluster.cattle.io/pod-security-version: "191456281"
  creationTimestamp: "2018-09-06T12:33:56Z"
  name: mycloud-psp
spec:
  allowPrivilegeEscalation: false
  allowedCapabilities:
  - NET_ADMIN
  - NET_RAW
  defaultAllowPrivilegeEscalation: false
  fsGroup:
    rule: RunAsAny
  runAsUser:
    rule: MustRunAsNonRoot
  seLinux:
    rule: RunAsAny
  supplementalGroups:
    rule: RunAsAny
  volumes:
  - secret
  - nfs
  - persistentVolumeClaim
  - configMap

Run the following command:

$ kubectl run -ti  my-busybox --image=busybox --restart=Never sh -n canh

Result:

Expect: due to enforced PSP, the pod creation should fail.
Actual: got the root shell command:

$ kubectl run -ti  my-busybox --image=busybox --restart=Never sh - canh

If you don't see a command prompt, try pressing enter.

/ # id
uid=0(root) gid=0(root) groups=10(wheel)
/ #

Other details that may be helpful:

RoleBindings in current namespace:

$ kubectl get rolebinding -n canh
NAME                                 AGE
clusterrolebinding-4spvd             28d
clusterrolebinding-scrlx             28d
default-mycloud-clusterrole-binding   63d

$ kubectl get rolebinding default-mycloud-clusterrole-binding -n canh -oyaml
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  annotations:
  name: default-mycloud-clusterrole-binding
  namespace: canh
  resourceVersion: "44254683"
  selfLink: /apis/rbac.authorization.k8s.io/v1/namespaces/canh/rolebindings/default-mycloud-clusterrole-binding
  uid: 7573283b-14c2-11e9-9e62-005056b1e4b1
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: mycloud-clusterrole
subjects:
- kind: ServiceAccount
  name: default
  namespace: canh

The cluster role  mycloud-clusterrole:

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
 annotations:
   serviceaccount.cluster.cattle.io/pod-security: mycloud
 creationTimestamp: "2018-09-06T12:33:56Z"
 labels:
   creator.cattle.io/rancher-created: "true"
 name: mycloud-clusterrole
 resourceVersion: "15658599"
 selfLink: /apis/rbac.authorization.k8s.io/v1/clusterroles/mycloud-clusterrole
 uid: 1ef88251-b1d1-11e8-a201-005056b1e4b1
rules:
- apiGroups:
 - extensions
 resourceNames:
 - mycloud-psp
 resources:
 - podsecuritypolicies
 verbs:
 - use

Verified that PSP was enabled in kube-apiserver:

# docker inspect kube-apiserver  | grep 'enable-admission-plugins'
            "--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,PodSecurityPolicy",
                "--enable-admission-plugins=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota,PodSecurityPolicy",

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): rancher v2.1.17
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): VMs, 10core, 72GB
Kubernetes version (use kubectl version):

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T19:44:10Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

# docker version
Client:
 Version:      17.06.0-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:20:36 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.0-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:21:56 2017
 OS/Arch:      linux/amd64
 Experimental: false

I cannot produce above bug in the other cluster running k8s v1.12.6, v1.12.3.

Update: I've tested on a clean k8s cluster v1.13.4 created by kubeadm and cannot reproduce the bug.
Some observations:

kube-apiserver:

# docker images | grep kube-apiserver
k8s.gcr.io/kube-apiserver            v1.13.4             fc3801f0fc54        3 weeks ago         181MB

# docker inspect k8s_kube-apiserver_kube-apiserver-k8s-master_kube-system_7256643a384d3ea77fa7a5f65dbc0ad9_0 | grep Image
        "Image": "sha256:fc3801f0fc5405d3c1ec02e7ed6f2fed84a8e4e22d3ef9583fcc67fd29878efe",
            "Image": "sha256:fc3801f0fc5405d3c1ec02e7ed6f2fed84a8e4e22d3ef9583fcc67fd29878efe",

PSP admission controller was enabled:

# docker inspect k8s_kube-apiserver_kube-apiserver-k8s-master_kube-system_7256643a384d3ea77fa7a5f65dbc0ad9_0 | grep admission
            "--enable-admission-plugins=NodeRestriction,PodSecurityPolicy",
                "--enable-admission-plugins=NodeRestriction,PodSecurityPolicy",

Execute kubectl run -ti  my-busybox --image=busybox --restart=Never sh -n canh stuck:

$ kubectl get pod -n canh
NAME                           READY   STATUS                       RESTARTS   AGE
my-busybox                     0/1     CreateContainerConfigError   0          7m44s
my-netutils-7f998dc698-vvjmd   0/1     CreateContainerConfigError   0          8m13s

$ kubectl describe pod my-busybox -n canh
...

  Normal   Scheduled  8m27s                   default-scheduler  Successfully assigned canh/my-busybox to node-1
  Normal   Pulled     6m48s (x8 over 8m24s)   kubelet, node-1    Successfully pulled image "busybox"
  Warning  Failed     6m48s (x8 over 8m24s)   kubelet, node-1    Error: container has runAsNonRoot and image will run as root
  Normal   Pulling    3m21s (x22 over 8m27s)  kubelet, node-1    pulling image "busybox"

I have a theory on what is happening. Here it is:

You ran that kubectl run command as a "cluster owner" (i.e. someone who has the been granted the cluster-admin role)
You have another PSP in that cluster that is more permissive (can confirm via kubectl get psp)
As a cluster owner, you have permissions to all resources, including that more permissive psp. So, when you create a pod directly, the kubernetes sees that you have proper access to the permissive PSP and thus allows you to create the pod.

Can you see if that checks out and let me know?

@cjellick : Thanks for your comment.
I create both users: admin (the user I used in the first post) and project-member, then do the test kubectl run -ti my-busybox --image=busybox --restart=Never with below scenarios:

k8s v1.12.3 or v1.12.6: for both admin and member users, the pod cannot be created with error CreateContainerConfigError, the annotation in the pod in both cases is kubernetes.io/psp: default-psp.

k8s v1.13.4:

project-member user: Annotation: kubernetes.io/psp: mycloud-psp, error: Error: container has runAsNonRoot and image will run as root
admin user: kubernetes.io/psp: default-psp, no error, can create pod running as root

So your guess is correct with k8s v1.13.4. It's good that the limited-user cannot create pod running as root.
However it's not clear to me why k8s v1.12.x can prevent admin running pod as root, but k8s-v1.13.4 cannot.

My guess is simply that through some other situation, the v1.12 cluster does not have a permissive PSP in in it. If you do kubectl get psp in the 1.12 cluster, what all is listed?

Rancher only deletes PSPs when the PSP Template that exists in the Rancher Global level is deleted and even then only if no projects are referncing it in the cluster.
So, a few things could have got you into this situation:

You currently have or previously had at least 1 project in the cluster referencing the permissive PSP.
Outside of Rancher, someone created a permissive PSP in the cluster that is completely unmanaged by Rancher.

FWIW, a cluster-admin has fully control in the cluster, so even if Rancher deleted the PSP, there's nothing to stop a cluster-admin from creating a new PSP and quickly and easily getting root access once again.

My guess is simply that through some other situation, the v1.12 cluster does not have a permissive PSP in in it. If you do kubectl get psp in the 1.12 cluster, what all is listed?

The 1.12.x clusters and 1.13.4 cluster both have the same list of PSP we defined via rancher server. So kubectl get psp in these clusters return the same 4-5 PSPs.

@canhnt should I close this issue then? Seems like we figured out what the root of the problem was then?

Thanks for your support. I think the issue can be closed.


Camera smoothing disabled in Scoresaber replays

When enabling FPFCToggle, Scoresaber replays will show exact headset position and rotation rather than smoothing them.
Also, camera pivot point will be screwed after exiting the replay.

Scoresaber replays will show exact headset position and rotation rather than smoothing them
This is not a problem with FPFCToggle. The 1.12.2 version of CameraPlus disables itself if it detects the FPFC launch argument, so it won't provide smoothing.
Also, camera pivot point will be screwed after exiting the replay.
I have fixed this internally and will be releasing the update soon.


Add reference to Microsoft.CodeAnalysis.CSharp

The language level currently doesn't have a reference to MS.CA.CSharp, which makes many things quite difficult, and resulted in a number of copy/pastes of utility functions from roslyn over to razor. This is the start of addressing that, adding a reference to MS.CA.CSharp and eliminating some of the simpler helpers that were copy/pasted. Contributes to https://github.com/dotnet/razor/issues/8445.

@dotnet/razor-compiler for review.

/azp run razor-tooling-ci


Changed the build type to ament_python and Fixed package to run with ros2 run

Fixed package to run with ros2 run rqt_service_caller rqt_service_caller. Related to this issue https://github.com/ros-visualization/rqt_console/issues/20
Signed-off-by: ahcorde<EMAIL_ADDRESS>

Running CI up-to rqt_service_caller

Linux
Linux-aarch64
macOS
Windows

One thing I noticed was that the "refresh" button does not have an icon; it's rendered as an empty button (I'm on Windows). I'm not sure if this is a bug introduced by this PR or an already existing bug. I'll try on Linux when I have a moment.

This bug is already present in 1.0.3 https://github.com/ros-visualization/rqt_service_caller/issues/19

I verified it can be ros2 run on Windows. All icons show up.
Running CI up to rqt_msg, rqt_srv, rqt_service_caller, rqt_top, rqt_shell, rqt_py_console, rqt_publisher, rqt_plot:

Linux
Linux-aarch64
macOS
Windows


Tried to force a dynamic response for: application/json but schema is not defined

User story.
As a Frontend engineer, I can do define an examples only without defining schemas, so that I can get response from HTTP request as well.
Is your feature request related to a problem?
When defining the YAML format, I only add the actual
responses:
        '200':
          content:
            application/json:
              examples:
                response:
                  value:
                     approval_type: manual
                     created_at: '2020-09-14T05:48:24.966971+00:00'
      # .... and so on

But when trying to execute the HTTP request below response returned instead.
{
    "type": "https://stoplight.io/prism/errors#UNKNOWN",
    "title": "Tried to force a dynamic response for: application/json but schema is not defined.",
    "status": 500,
    "detail": ""
}

I'm assumed that this is because I didn't define a schema like this

Describe the solution you'd like
Is it possible for prism to generate response for application/json based on the examples only to reduce step defining schema for our teams (frontend)
Additional context
Add any other context or screenshots about the feature request here.

Hey,
I am not exactly sure what you're trying to achieve; what does it mean for you to return a dynamic example — if there's no schema (and thus examples cannot be generated?)
Do you mean randomly returning the defined examples?

Does the Prism is necessary to define schema so the request can be executed correctly?
We're defining our Mock API previously using apiary.io, then using api-spec-converter library to convert from api_blueprint to openapi_3.
The result is YAML generated the examples without schemas block, but compiles correctly in editor.swagger.io.
Afterward we're trying to create simple API Description using YAML, with schema block, defining the object and its properties, the Prism able to return correct response.
Otherwise, without schema block the Prism return the above 500 error instead

Dynamic mode requests a schema to work, as it generated the dynamic example from a schema.
https://meta.stoplight.io/docs/prism/docs/guides/01-mocking.md
You can use static mode which is default for Prism CLI, or can be picked with the Prefer header for Prism running in other modes (hosted, try it now, etc).

Exactly — @mochadwi just run Prism without the dynamic flag and then either select your example using the Prefer header or let it return the first one for you.
Feel free to reopen or comment if you need further clarifications.

@XVincentX @philsturgeon does the static mode, applied for all endpoint defined, or we can we specified which endpoint dynamic/static?

does the Prefer: static for that specific endpoint we hit, means will generate a response from examples?

UPDATES:
Results for Prefer: dynamic=true (why this issue opened in the first time):

Result for Prefer: dynamic=false (solving our issue, thus this issue closed):

Both of the above response is runs by -d argument when running Prism locally. Thus I assume, when configured in our Mock Server, this also fixed our issue
Thanks @XVincentX & @philsturgeon for your answer


Can't re-request a team invite after leaving team

Steps to Reproduce

User requests an invite to team.
Invite is ignored. (Maybe accidentally.)
If the user re-requests an invite, it fails with "▶ ERROR access already requested (code 2663)" (As expected. This is likely to protect against spamming/abuse.)
Admin manually add user to the team.
User leaves team.
User re-requests invite.
"▶ ERROR access already requested (code 2663)"

Expected Results
After a user has been in a team, he/she should be able to leave the team and later request to join the team again.
Elaboration
Once a team invite request is ignored (either intentionally or unintentionally) neither the admin nor the other user can recover from that state.

The admin (AFAICT?) can't list "ignored" invite requests to later accept them via their token.
The user can't re-request an invite to the team.
Even if the admin manually adds the user to the team (somehow remembers their username) the bad state will persist if the user ever leaves the team.

@zapu  can you triage this one

@NfNitLoop I can confirm the issue, I've reproduced this today. Thank you for your report, we are on it.

@NfNitLoop this should be fixed now, although we did not go and fix the statuses of old team access requests that might be invalid. If there are some specific teams that suffer from this greatly and you'd like to have them fixed, let me know. Thanks!


Print header if t=0.

Print the header also if t = 0. In this case, the dual_gap is good enough from the get go and we do not enter the while loop. Nevertheless, the header should be printed.

Codecov Report

Merging #356 (0ab97e1) into master (0e20791) will decrease coverage by 0.19%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #356      +/-   ##
==========================================
- Coverage   86.90%   86.71%   -0.20%
==========================================
  Files          17       17
  Lines        1947     1919      -28
==========================================
- Hits         1692     1664      -28
  Misses        255      255

Impacted Files
Coverage Δ

src/callback.jl
95.65% <100.00%> (-0.19%)
:arrow_down:

src/abstract_oracles.jl
86.45% <0.00%> (-0.80%)
:arrow_down:

src/utils.jl
81.06% <0.00%> (-0.43%)
:arrow_down:

src/types.jl
84.69% <0.00%> (-0.36%)
:arrow_down:

src/blended_cg.jl
84.91% <0.00%> (-0.33%)
:arrow_down:

src/active_set.jl
93.49% <0.00%> (-0.11%)
:arrow_down:

src/polytope_oracles.jl
92.22% <0.00%> (-0.09%)
:arrow_down:

src/norm_oracles.jl
95.53% <0.00%> (-0.08%)
:arrow_down:

src/linesearch.jl
90.54% <0.00%> (-0.07%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


Minor typos and links.

Very minor update of 1) a typo and 2) to the LICENSE file. Just want to get this going while I figure out #52 on the side. Thanks!

LGTM; thanks!


Saving complex scene with multiple exports var statements and instanced sub-scenes takes up to minutes

Godot version:
3.2.3-stable-official, also tested with 3.2.4-beta1
OS/device including version:
Windows 10
Issue description:
Saving a scene in the MRP takes up to couple of minutes, making editing it unusable. Editor is stuck unresponsive at:

Steps to reproduce:

Open MRP
Open res://comms/conversation/MinerConversation.tscn
Save the scene.

Scene should save in fraction of the second, but it hangs on application unresponsive for minutes, making editing the game unpractical. It also happens to every scene this one is instanced in, including "Load as Placeholder" option.
Minimal reproduction project:

slow-saving-mrp.zip
Notes
All the nodes in the scene are instance of same class - it's a representation of dialog tree of the game. I was able to determine that it's somehow related to export var statements - if you remove them from res://comms/ConversationPlayer.gd scene saves with expected speed.
I was not able to produce a synthetic MRP, so this above is stripped-down dialog tree directly from ΔV: Rings of Saturn.

The editor also freezes when you open and close a script from any node.

I wonder if this is fixed in master?

Unfortunately master requires a separate MRP, because exports are incompatible.

@fire still happening with master / 50da616eeb.
MRP for master: slow-saving-mrp-master.zip

I investigated this issue a bit and tracked it down to this method:
https://github.com/godotengine/godot/blob/5bb7c7c367c1df7257164053b85d01dcf1406f45/core/script_language.cpp#L482-L524
Placing return at the top will remove the long loading time, not sure why or how to fix it. Could be a good starting point for someone else to give a shot at fixing the issue.
Also here's better MRP for master, because the above one is invalid:
slow-saving-mrp-master.zip

I narrowed it further down to this:
https://github.com/godotengine/godot/blob/5bb7c7c367c1df7257164053b85d01dcf1406f45/core/script_language.cpp#L518

Weird, because I checked that and removing it made no difference.

@KoBeWi you are right, I jumped to a conclusion there, sorry.

I narrowed cause of slow saves is here:
https://github.com/godotengine/godot/blob/61c8efecffd52953da621566df2033ecce0710d5/editor/editor_node.cpp#L1428-L1435
...which was introduced by 383dea5796d791c89678fe1aea384d42e9f3de8d (with later changes)

As a workaround I just removed that part from my version of the engine and I can work again, but I suppose it re-introduces the sub-inheritance bug @RandomShaper fixed with that.

Allow me to demonstrate the scale of the problem in 3.3-rc8. This video shows opening and saving scene once, in realtime. It takes 5 minutes to open the scene and over 15 minutes to save it (for each save): https://youtu.be/U-Ut_7x1uWA

I wonder what problem was the dummy scene supposed to solve. I only found #7984 and #7976. The former is still valid actually, the latter doesn't have clear reproduction steps.

#47828 would only fix the slow saving, in my tests it still takes ages to open the scene in the MRP.
Since it might introduce regressions and it's pretty late, I made a version for 3.x which adds a project setting to allow disabling the offending save code: https://github.com/akien-mga/godot/tree/3.x-opt-out-node-paths-update
But if it doesn't help with loading that scene, it seems the problem is deeper than that.

Not sure if that's any help, but I observe similar slowdowns also when I am renaming objects in tree.

I think debugging the slow opening for this specific scene should help figure out what the real bug is, and possible solve all symptoms at once (slow opening, slow saving, slow renaming).
It seems to spend a lot of time creating placeholder instances for each instantiated scene and there's plenty of them with multiple levels of sub-instances, which seems to trigger a pathological case:
(gdb) bt
#0  0x0000000001735626 in PropertyInfo::operator= (this=0x12c9b060) at ./core/object.h:144
#1  0x0000000001735775 in List<PropertyInfo, DefaultAllocator>::push_back (this=0x12a00290, value=...) at ./core/list.h:229
#2  0x00000000017f4259 in List<PropertyInfo, DefaultAllocator>::operator= (this=0x12a00290, p_list=...) at ./core/list.h:462
#3  0x00000000042e9179 in PlaceHolderScriptInstance::update (this=0x12a00280, p_properties=..., p_values=...) at core/script_language.cpp:576
#4  0x00000000017ddf86 in GDScript::_update_exports (this=0xc6439e0, r_err=0x0, p_recursive_call=false) at modules/gdscript/gdscript.cpp:512
#5  0x00000000017dcf4a in GDScript::placeholder_instance_create (this=0xc6439e0, p_this=0x12ee6600) at modules/gdscript/gdscript.cpp:331
#6  0x000000000429cdb2 in Object::set_script (this=0x12ee6600, p_script=...) at core/object.cpp:1030
#7  0x0000000004299c2d in Object::set (this=0x12ee6600, p_name=..., p_value=..., r_valid=0x7fffffff83bf) at core/object.cpp:433
#8  0x0000000003c1c5de in SceneState::instance (this=0xc63fd80, p_edit_state=SceneState::GEN_EDIT_STATE_INSTANCE) at scene/resources/packed_scene.cpp:213
#9  0x0000000003c2740c in PackedScene::instance (this=0x129673b0, p_edit_state=PackedScene::GEN_EDIT_STATE_INSTANCE) at scene/resources/packed_scene.cpp:1703
#10 0x0000000003c1bba3 in SceneState::instance (this=0x1296b580, p_edit_state=SceneState::GEN_EDIT_STATE_INSTANCE) at scene/resources/packed_scene.cpp:141
#11 0x0000000003c2740c in PackedScene::instance (this=0x1296c820, p_edit_state=PackedScene::GEN_EDIT_STATE_INSTANCE) at scene/resources/packed_scene.cpp:1703
#12 0x0000000003c1bba3 in SceneState::instance (this=0x129644f0, p_edit_state=SceneState::GEN_EDIT_STATE_INSTANCE) at scene/resources/packed_scene.cpp:141
#13 0x0000000003c2740c in PackedScene::instance (this=0x12961450, p_edit_state=PackedScene::GEN_EDIT_STATE_INSTANCE) at scene/resources/packed_scene.cpp:1703
#14 0x0000000003c1bba3 in SceneState::instance (this=0x12975340, p_edit_state=SceneState::GEN_EDIT_STATE_MAIN) at scene/resources/packed_scene.cpp:141
#15 0x0000000003c2740c in PackedScene::instance (this=0xc643e20, p_edit_state=PackedScene::GEN_EDIT_STATE_MAIN) at scene/resources/packed_scene.cpp:1703
#16 0x0000000002a88734 in EditorNode::load_scene (this=0x7f0dda0, p_scene=..., p_ignore_broken_deps=false, p_set_inherited=false, p_clear_errors=true, p_force_open_imported=false, p_silent_change_tab=false)
    at editor/editor_node.cpp:3623
#17 0x0000000002a88f5f in EditorNode::open_request (this=0x7f0dda0, p_path=...) at editor/editor_node.cpp:3685
<cut rest of the backtrace, not relevant>

Won't have time to debug further for now, anyone is welcome to pick it up from here.

I'd like to chime in to say that this is an issue for me as well, and removing the dummy scene does in fact make saving the scene become basically instantaneous.


Use prettier

There are many reformats in the last pull requests.
If we use a code format tool like prettier we could prevent that.
What do you think? I could make a pull request for this.

I definitely support using eslint with a pre-commit hook at a minimum. I haven't dealt with prettier, it seems a little intense.
If you want to do prettier instead I'd probably be okay with whatever (sensible) rules you choose.

Pre-commit with prettier would be pretty good
Could also add a linting step to the CI

We can use https://github.com/hexacta/prettier-check for checking the style in CI.
Do you all agree witch switching to eslint?

I'm OK with eslint or prettier, just wondering @n1ru4l if you intend to extend prettier rules. If not then we can just use prettier directly. I would prefer to adopt a widely used ruleset with strictly no additional opinion (prettier, airbnb, standard, etc). I don't want to see contributors discussing styling preferences frequently, it takes away focus on real issues.

@leontastic I would say we use the default prettier config. With https://github.com/prettier/eslint-config-prettier to disable all eslint rules that conflict with prettier.
I am not sure about the eslint config.. eslint:recommended might be enough.

I guess what I'm not getting is why we need eslint at all if prettier can be run directly. Is it just for IDE integration?

Because prettier is about code formatting and eslint is more about linting e.g. no unused declarations.
We could also continue using jshint but I do not want to spend my time disabling every rule that conflicts with prettier 😅

Doing more reading into it I think @n1ru4l is right – it would be prudent to use both, eslint for enforcing consistent syntax and prettier for consistent formatting.
I'm a big fan of standard. But I don't have a strong opinion since this is an open-source repo anyway – we can start with eslint:recommended for simplicity if we don't all have the same preferences.

grrr standard. I'm fine with just eslint:recommended.


What is the left

Jobs
Front-end
assigned to

[ ] Admin page
[ ] Index page
[ ] Apply basic designs

Back-end
assigned to @tigris24

[x] Login session #4
[ ] meow

Blockchain
assigned to @TwoPair

[x] Peer deploying in Docker
[ ] Ticket, Event class draft for chaincode
[ ] Release chaincode to peers

[ ] local
[ ] with Gateway

front-end
maybe need personal information management page to modify member's information
back-end
modify member's information
check member's information by manager
logout and session delete
these operations are going to be added

back-end
already implemented

connect to couch-base and exchange data by using Cluster
use two buckets for saving data about seat and user information
access control to page according to privilege
seat data initialize with starting application and delete with closing application

[BackEnd]

Completion list

session control
logout
member info in manager system
exception

Additional Completion list

redirect to index when logout or session out
check and restrict login attempt
add seat service and event service

seat create/delete when event make/erase
user can reserve up to two tickets
manager can check user who reserve some ticket about his event

most of existing code on controller class are refactoring as methods of proper service class

reCAPTCHA is not done


Getting another type of picker instead the one shown in the demo page

Hi,
When i click on the cell to edit the date the first time, i'm getting this indesirable picker instead the one shown in the demo page.
How i can get rid of it and get this one and get back the other picker as in the demo?
the htlm tag looks like this
<div moment-picker="row.entity.values[\'' + col.id + '\'].value" format="MMM Do YYYY" min-view="year" max-view="month" start-view="month" autoclose="true" today="true" keyboard="true"> {{ grid.appScope.formatMe(grid.getCellValue(row, col), col.colDef.year) || \'Click here to select a date\' }} </div>
Cheers

Hi @Bartaf83, this is because you are using input with type="date", so the every browser uses its own implementation of a date input. To avoid this, you just need to set input type to text or just remove the type property (so that the browser fallback to text type).

Thanks ! i will try that but as you see i'm not using the tag with the input (but now i ll try to use it and change its type to text)

Mmm, it quite impossible that the template you've sent will open the classic browser calendar.
Also, <div> tag is not editable, but in the screenshot you have the focus on a field!

i'm using the datepicker inside the angular ui grid , that's why there is the focus

So, you have to handle with Angular UI grid for date editing. Don't know if you can set a custom template to be sure you are using Angular Moment Picker, but I'm enough sure that this field is not using Moment Picker directive.


Zooming scroll view does not accept swipe when zoomed and reused.

I'm running into an issue where pages that were zoomed often do not accept swipes to scroll to the next page when they are reused. I can swipe on the "black bars" above and below the image, but swiping on the image does not cause the outer scroll view to scroll.
Is there something I need to do to reset the zooming scroll page before it is reused?

Are you resetting the zoom level back to 1 when you update the reusable page content? The BRScrollerDemo's AsyncPhotoViewController and PdfViewController examples are both cases where the page views are scroll views, which sounds similar to your setup. They both end up calling something along the lines of
[pageScrollView setZoomScale:1 animated:NO];

when the content is updated for a page.

I've implemented the scroller:willDisplayPage:view as follows. However, the content area with the photo does not scroll when swiped.
- (void)scroller:(BRScrollerView *)scroller
 willDisplayPage:(NSUInteger)index
            view:(UIView *)reusablePageView {
    BRZoomingImageView *zoomer = (BRZoomingImageView *)reusablePageView;
    zoomer.tag = index;
    [zoomer setZoomScale:1.0 animated:NO];
    MyModel *model = _models[index];
    zoomer.imageView.imageURL = [NSURL URLWithString:model.remoteURL];
}

Is this the right delegate method?

That is the right delegate method, yes, and looks like you're doing the same as the demo so that all looks fine. Have you run that demo, and does the demo work OK for you on the same device you're testing on? What does your createReusablePageViewForScroller: implementation look like?

Currently, it looks like
static int colorIndex = 0;

- (UIView *)createReusablePageViewForScroller:(BRScrollerView *)scroller
{
    NSLog(@"Color Index: %d", colorIndex);

    UIColor *bgColor = nil;

    switch (colorIndex) {

        case 0:
            bgColor = [UIColor redColor];
            break;
        case 1:
            bgColor = [UIColor greenColor];
            break;
        case 2:
            bgColor = [UIColor blueColor];
            break;
        case 3:
            bgColor = [UIColor purpleColor];
            break;
        case 4:
            bgColor = [UIColor orangeColor];
            break;
    }

    BRZoomingImageView *zoomer = [[BRZoomingImageView alloc] initWithFrame:scroller.bounds];
    zoomer.imageView.delegate = self;
    zoomer.scrollDelegate = self;
    zoomer.imageView.imageContentView.delegate = self;
    zoomer.directionalLockEnabled = YES;
   // zoomer.doubleTapToZoom = YES;
    zoomer.backgroundColor = bgColor;
    zoomer.showsVerticalScrollIndicator = NO;
    zoomer.showsHorizontalScrollIndicator = NO;

    colorIndex++;
    if (colorIndex > 4) {
        colorIndex = 0;
    }
    return zoomer;
}

I was able to correlate between having previously zoomed the view and loosing swipe functionality when refused by setting them to have different background colors.
First, I disabled user interaction on everything but the zooming scroll view. this didn't seem to have any effect. Next I added...
- (void)touchesBegan:(NSSet<UITouch *> *)touches withEvent:(UIEvent *)event
{
    NSLog(@"Touches began in zooming scroll view");
    [super touchesBegan:touches withEvent:event];
}

To the zooming scroll view. The zooming scroll view receives touchesBegan:withEvent: calls when swiping fails, which indicates the gesture recognizer is not receiving touches.
On a hunch, I completely commented out gestureRecognizer:shouldReceiveTouch: in BRCenteringScrollView as swipes in the non-image areas continued to work even if the previous page had been zoomed. However, this still did not solve the problem.
If I add....
-(BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldRecognizeSimultaneouslyWithGestureRecognizer:(UIGestureRecognizer *)otherGestureRecognizer
{
    return YES;
}

This allows both scroll views to scroll at the same time, but the main scroll view scrolls along with the image scroll view, which is not the desired behavior.

"That is the right delegate method, yes, and looks like you're doing the same as the demo so that all looks fine. Have you run that demo, and does the demo work OK for you on the same device you're testing on?"
The demo runs correctly across devices and simulators. The issue I'm seeing is consistent across both as well. My use case is differs in that both preview and full resolution images are remote, rather than local. This does not seem to be a good fit as the delegate methods ofrenderPreviewImageForView:key:atSize: and previewImageForView:atSize: expect UIImages to be returned at the end of the method call.

After digging deeper, I've discovered that zoomed reused pages receive calls to touchesBegan: after the custom accessor setContentOffset: is called on BRCenterScrollingView. If the page has not been previously zoomed, touchesBegan is not called on the zooming scroll view. Commenting out setContentOffset: results in the image hugging the upper left corner of the scroll view, but scrolling works even after zooming.
2015-11-03 02:14:12.570 appName[74455:18662704] touchesMoved >>>>>>>>
2015-11-03 02:14:12.570 appName[74455:18662704] <UIScrollViewDelayedTouchesBeganGestureRecognizer: 0x7f8e3a4bd5f0; state = Possible; delaysTouchesBegan = YES; view = <BRZoomingImageView 0x7f8e3b0aa000>; target= <(action=delayed:, target=<BRZoomingImageView 0x7f8e3b0aa000>)>>
2015-11-03 02:14:12.570 appName[74455:18662704] <UIScrollViewPanGestureRecognizer: 0x7f8e3a44e4e0; state = Possible; delaysTouchesEnded = NO; view = <BRZoomingImageView 0x7f8e3b0aa000>; target= <(action=handlePan:, target=<BRZoomingImageView 0x7f8e3b0aa000>)>>
2015-11-03 02:14:12.571 appName[74455:18662704] <UIScrollViewPinchGestureRecognizer: 0x7f8e3a5b30f0; state = Possible; delaysTouchesEnded = NO; view = <BRZoomingImageView 0x7f8e3b0aa000>; target= <(action=handlePinch:, target=<BRZoomingImageView 0x7f8e3b0aa000>)>>

What seems odd is that the same content offset is being reported when the page is first displayed (and scrolling works) and when reused (and scrolling no longer works). What's different is that the zooming image view receives touchesBegan which, AFAIK, should not occur due to the UIScrollViewDelayedTouchesBeganGestureRecognizer

I am curious what ends up being different in the way your app is running versus the demo app (which works OK). Perhaps there is something to the use of remote images, but I'm not quite sure. The image preview methods are called from background threads, are you by chance manipulating any of the view hierarchy in those callbacks?
Do you have a small stand-alone app that demonstrates the problem that you could share? Even if you just forked the repo and added a new example to the demo app that exhibited the problem, that would be very helpful for investigating the cause of the issue.

I have wrapped calls that access the view hierarchy in GCD blocks running on the main queue, so I don't suspect that is the issue.
I do not have a stand alone at to demo at this time. Ended up moving to a custom UIPagingViewController solution due to time constraints.

OK, I'll close this ticket then as I don't have a reproducible test case.


Use upstream niv-updater-action again

Now that knl/niv-updater-action#46 is merged, use the official upstream repo.

This PR does not affect the produced WebAssembly code.


How to deal with multiple pages?

Here is my app looks like:
angular2-webpack-starter/
 ├──config/                        * configuration
 │
 ├──src/
 |   ├──main.browser.ts
 │   │
 |   ├──index.html          * Index.html: The main entry of the app,which visted by localhost:3000.
 │   │
 │   ├──admin/              * Admin module floder
 │   │    └──index.thml     * This file is Admin module entry,I wanna visit by localhost:3000/admin
 │   └──assets/
 │
 ├──tslint.json
 ├──typedoc.json
 ├──tsconfig.json
 ├──tsconfig.webpack.json
 ├──package.json
 └──webpack.config.js

I wanna visit admin module by http://localhost:3000/admin ,
and Here is webpack configs:
//webpack.dev.js
devServer: {
 port: METADATA.port,
 host: METADATA.host,
 historyApiFallback: {
    rewrites: [
   // rewrite url so I can visit localhost:3000/admin instead of localhost:3000/admin/index.html
   { from: /^\/admin/, to: '/admin/index.html' },
],
 },
 watchOptions: {
   aggregateTimeout: 300,
   poll: 1000
 }
},

//webpack.common.js add a plugin for /admin/index.html
 new HtmlWebpackPlugin({
   template:'src/admin/index.html',
   title: METADATA.title,
   chunksSortMode: 'dependency',
   metadata: METADATA,
   inject: 'head',
 }),

But actually the scripts and header tags not inject to /src/admin/index.html page,just some <%  XXXX) { %> <% } %>syntax,so how to deal with this situation?
Thanks.

If your admin module is an NgModule you could add it to your app's routes. Look at the relationship between src/app/+detail/detail.module.ts and how it's loaded in src/app/app.routes.ts.
You'll need to create a path linking /admin with your module.
  { path: 'admin', loadChildren: './+admin#AdminModule'},


VS Code Debugger shows incorrect Variable fields

Describe the bug
VS Code sometimes shows incorrect variable fields in the debugger: the first screenshot shows a record variable TempAddress of type "NVT Transportaddress". Below the variable the fields ("Entry No.", "Anomaly Type",...") are displayed.  The second screenshot shows the actual fields of the "NVT Transportaddress" table: the fields "Entry No.", "Anomaly Type",... are nowhere to be seen in this table. In fact, the debugger shows the variables of the Rec variable (in which a function using the "NVT Transportaddress" function is present (see third & fourth screenshot).
To Reproduce
(See Screenshots & info above)
Expected behavior
The debugger shows the correct fields for a variable
Screenshots

5. Versions:

AL Language:
Name: AL Language
Id: ms-dynamics-smb.al
Description: AL development tools for Dynamics 365 Business Central
Version: 5.0.229698
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dynamics-smb.al

Business Central:
Version: W1 15.2 (Platform 15.0.38951.0 + Application 14.0.29530.0)

Do you by any chance have another global variable called TempAddress or any variable that may be in scope and is called like that?

Do you by any chance have another global variable called TempAddress or any variable that may be in scope and is called like that?

Not that I can see. All other TempAddress variables are of the record type "NVT Transportaddress" anyway. Ihave this issue quite frequently. I can send you another sample if I encounter it again.

I have meant whether the name TempAddress is already used in the document's scope. If yes that is the issue and it is by design. The type does not matter for the debug engine, only the scope. If you have a variable with the same name in global scope that takes precedence in evaluation. If possible try using different names for your variables.

I have meant whether the name TempAddress is already used in the document's scope. If yes that is the issue and it is by design. The type does not matter for the debug engine, only the scope. If you have a variable with the same name in global scope that takes precedence in evaluation. If possible try using different names for your variables.

That makes since and I'm aware of that. But this is not the case in the sample above.

If you can find a simple repro it would help us fixing the issue. Otherwise it is just guessing.

If you can find a simple repro it would help us fixing the issue. Otherwise it is just guessing.

I've just created a sample but the issue does not occur at this point. We've had this problem at multiple occasions, but reproducing will be quite hard I'm afraid. I'll try to provide some extra samples when it occurs again. It might have something to do with WITH statements (of which we use plenty), but I'm not 100% sure.

I am closing this issue because it appears that it has been resolved. Please open a new issue if you believe this has not been resolved and reference the current issue.


Unify image colors

The repository image in Search is grey, but in Bookmarks it is blue.

so what to change here.
Option 1: Bookmarks image color to grey
Option 2: Search repo image color to blue

I would opt for blue!

I would opt for blue as well. Let's hear from @rnystrom as well.

Blue sounds good. Should prob also add the icon to actual search results too.
Sent with GitHawk


import series seed template

similar to the yc_aa template.
we need a better way to do amendment & alteration of articles of association.

this has been imported and is being used for Fynd's investment round, also for Voost.