UDP Appender to have pattern configurability

Referencing #72 :
"I realize it's a little confusing. I'd like to make the UDP appender be configured just like the TCP appender (and most every other logback appender). Meaning, you would have to configure a layout/encoder within the appender. However, I can't change it due to backwards compatibility issues."
How about introducing a new UDP appender that extends LogstashSocketAppender with the above functionalities? I know that it hurts symmetry, but it would be really useful. We would like to customize the output with the power of CompositeJsonEncoder, yet not give up the speed of UDP.
If this is not in your roadmap, how would you suggest implementing this to remain inline and compatible with your future releases?

Hi @gsziklai,
It is somewhat possible to use the pattern provider with the LogstashSocketAppender today.  Although, it's a bit of a hack, and not at all ideal.
For example:
<appender name="stash" class="net.logstash.logback.appender.LogstashSocketAppender">
  <host>MyAwesomeSyslogServer</host>
  <port>514</port>
  <provider class="net.logstash.logback.composite.loggingevent.LoggingEventPatternJsonProvider">
    <pattern>
        {
          "foo": "bar"
        }
    </pattern>
  </provider>
</appender>

To implement this a bit better, I would probably insert a class in the hierarchy between SyslogAppenderBase and LogstashSocketAppender that took any type of Layout.
LogstashSocketAppender is highly tied to a LogstashLayout, so extending LogstashSocketAppender would not be the best option if a different layout was used.
I haven't thought through the complete implementation, but that's just what comes to mind first.  If you want to give it a shot, please feel free to submit a pull request.  I probably won't be able to get to it for a while.

Thank you. The configuration option you provided works for us.


ssh alias not Working

VSCode Version: Code 1.8.1 (ee428b0eead68bf0fb99ab5fdc4439be227b6281, 2016-12-19T14:42:49.304Z)
OS Version: Darwin x64 16.3.0
Extensions:

Extension
Author
Version

rainbow-brackets
2gua
0.0.6

crane
HvyIndustries
0.2.2

html-css-class-completion
Zignd
1.0.3

githistory
donjayamanne
0.1.4

rest-client
humao
0.11.4

debugger-for-chrome
msjsdiag
2.4.2

indent-rainbow
oderwat
0.4.1

laravel-blade
onecentlin
1.5.0

view-in-browser
qinjia
0.0.3

vscode-icons
robertohuertasm
6.0.0

laravel-artisan
ryannaddy
0.0.3

Steps to Reproduce:

open built in terminal
type my ssh alias
command not found error

A few quick questions to help investigate:

Which terminal are you using? Bash?
How did you define the aliases? In an ~/.aliases file?

I confirmed that I also do not see aliases from ~/.aliases being recognized on Mac. @Tyriar Any thoughts?

You probably need to run as a login shell by adding this to settings.json:
"terminal.integrated.shellArgs.osx": ["-l"]

See https://code.visualstudio.com/docs/editor/integrated-terminal#_linux-os-x


about laravel 5.8 problem

Hi, thank for you share this component
I use the laravel5.8, and front-end use the Vuejs2, but I dont know how to use your component in my Vue.

https://github.com/andyleach/vue-flash/blob/master/readme.md


Added ematipico to the core contributors team

As per title, adding myself to the core contributors team.
Updated GOVERNANCE.md and team.md

Yessss! The list is alphabetical so you can move yourself up. We should make the team page randomize order on load though. Should be easy with some JS magic, I'll open an issue.

So excited to have you @ematipico!


Cargo prints steps out of order

Consider this output for cargo install cargo-fuzz:
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading cargo-fuzz v0.1.0
  Installing cargo-fuzz v0.1.0
 Downloading docopt v0.7.0
 Downloading cargo_metadata v0.1.2
 Downloading regex v0.2.1
 Downloading thread_local v0.3.3
 Downloading regex-syntax v0.4.0
 Downloading memchr v1.0.1
 Downloading utf8-ranges v1.0.0
 Downloading aho-corasick v0.6.2
 Downloading serde_derive v0.9.7
 Downloading serde_json v0.9.8
 Downloading syn v0.11.6
 Downloading serde_codegen_internals v0.13.0
 Downloading quote v0.3.13
 Downloading unicode-xid v0.0.4
 Downloading synom v0.11.0
   Compiling strsim v0.6.0
   Compiling quote v0.3.13
   Compiling libc v0.2.20
   Compiling num-traits v0.1.36
   Compiling utf8-ranges v1.0.0
   Compiling void v1.0.2
   Compiling rustc-serialize v0.3.22
   Compiling serde v0.9.7
   Compiling unreachable v0.1.1
   Compiling lazy_static v0.2.2
   Compiling regex-syntax v0.4.0
   Compiling thread-id v3.0.0
   Compiling memchr v1.0.1
   Compiling thread_local v0.3.3
   Compiling unicode-xid v0.0.4
   Compiling itoa v0.3.1
   Compiling synom v0.11.0
   Compiling aho-corasick v0.6.2
   Compiling dtoa v0.4.1
   Compiling syn v0.11.6
   Compiling serde_json v0.9.8
   Compiling regex v0.2.1
   Compiling serde_codegen_internals v0.13.0
   Compiling serde_derive v0.9.7
   Compiling docopt v0.7.0
   Compiling cargo_metadata v0.1.2
   Compiling cargo-fuzz v0.1.0
    Finished release [optimized] target(s) in 58.30 secs
  Installing #####################

Now, the first two steps say:
 Downloading cargo-fuzz v0.1.0
  Installing cargo-fuzz v0.1.0

So, it is installing the thing even before it is compiled; that’s obviously not true, so assume that its printed before all the steps that are necessary to actually install it (such as downloading dependencies and compiling the binary) are started.
However at the same time, compiling step is printed after the downloading step – which sort of is an inverse of above observation.
I feel like I’ve observed somewhat related inconsistencies while using rustbuild wherein printout Compiling crate does not necessarily reflect the fact of build for this crate being started.

For rustbuild, you're probably running into https://github.com/rust-lang/cargo/issues/833


General repo cleanup

removed TODOs
refreshed README using --about --format=markdown output
clear commented out cookiecutter code blocks

@prratek @hkuffel let me know what you think!

Thanks for this @pnadolny13!


Feature request - allow throwing rocks.

Like snowballs.

I don't think this would fit my vision for the mod, but I'll leave it up for debate.

I like the skipping rock function in the Campanian mod. Perhaps you could make the rocks in this mod work as skipping rocks with that mod, or you can just make them work as skipping rocks vanilla (as in, only with ThisRocks without Campanian.)


log levels not working

Even with the following code I still get undesired logs (e.g. INFO, LOG, etc.):
const logger = connect.getLog();
logger.setLogLevel(connect.LogLevel.CRITICAL);
logger.setEchoLevel(connect.LogLevel.CRITICAL);

This is a known issue, unfortunately setting the log level doesn't work. We have a backlog task to fix this.

@tannera926 is this a task/issue I can follow on GitHub to track progress or is it in a private issue tracking system? If not public, can we leave this one open until it is fixed?

This isn't a task you can follow on Github. If you would like it to be prioritized, you can submit a feature request to support here.


find references

I'd like to have this working properly (i.e. not only in current file).
@Simn how it should be done wrt haxe? should languageserver maintain the list of .hx files in the project, be aware of classpaths and convert those files to qualified module paths and pass them to haxe compiler?

I was thinking to utilize --macro include somehow but you easily run the risk of including stuff that is not meant to be used on the current target. I'm inclined to think that usage completion really requires a normal build step through the compilation server first.

Moved to https://github.com/vshaxe/vshaxe/issues/96.


Updated Java package tutorial instructions

Correct the expected value of the @Package/repository value
Mention the need for the @Package/publish=true field
Removed use of the @Runtime/publicAddress field since the tutorial does not appear to be ACI specific
Correct the type of service created on the remote Kubernetes cluster

LGTM, thanks!


Investigate why TbdexTestVectorsProtocol tests runs extremely slow sometimes and fix it

TbdexTestVectorsProtocol tests that involves JSON parsing SOMETIMES take insane amount of time (~5 seconds per test) to complete causing test timeout failures.
Glancing over the code however I don't see why it'd take milliseconds to complete sometimes and 10x or even 100x some other time. But this causes our CICD pipeline to fail with a misleading error because the test log are hidden when run using pnpm (there might be a config to expand it, but that's a separate issue):

and it is fine when running locally?

@michaelneale, this appears must more rarely locally, but I have seen it when I inherited the repo and was very puzzled by it, but never reproduced it twice in a row.

I think it is the mocha xml reporter that blows up - I saw it locally a bit too, couldn't work out why. XML isn't a great format for streaming results and can blow up in memory but not sure in this case?
https://github.com/TBD54566975/tbdex-js/pull/255 I have run that several times with no issue with the default spec reporter

tried updating to latest mocha stuff - same issue.

certtainly seems related to xml reporting.

I think #257 should do the job.

#257 addresses this, closing.


Method not found: 'System.Threading.Tasks.Task`1<!0>

I'm trying to send a message to a queue from an .NET Framework 4.7.2 app and am getting on the call to sender.SendMessageAsync
Method not found: 'System.Threading.Tasks.Task1<!0> Microsoft.Azure.Amqp.Singleton1.GetOrCreateAsync(System.TimeSpan, System.Threading.CancellationToken)'.
I am using Azure.Messaging.ServiceBus 7.7.0. We haven't been having this issue for messages sent from our .NET Core 3.1 and .NET 6 function apps.
Is there something additional that needs to be considered when trying from a .NET Framework project?

Hi @RyFive85.  Thank you for reaching out and we regret that you're experiencing difficulties.  It should be possible to use the client library from .NET Framework 4.7.2.   Our test runs include net461 as a target platform, and they're passing.   I've also attempted to repro locally using net472 and I'm able to publish and consume messages.
Would you be so kind as to include the set of error details, including the stack trace?   If it is possible for you to package a minimal repro, that would be extremely helpful.  Without the repro, our next best step would be to collect SDK logs so that we can understand the client perspective.  Details for doing so can be found in this sample.

@jsquire to start, here is the stack trace:
at Azure.Messaging.ServiceBus.Amqp.AmqpSender.d__19.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at Azure.Messaging.ServiceBus.Amqp.AmqpSender.SendBatchInternalAsync(IEnumerable1 messages, TimeSpan timeout, CancellationToken cancellationToken)    at Azure.Messaging.ServiceBus.Amqp.AmqpSender.<>c.<<SendAsync>b__20_0>d.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.<>c__201.<b__20_0>d.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.<RunOperation>d__212.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.d__212.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Azure.Messaging.ServiceBus.ServiceBusRetryPolicy.<RunOperation>d__201.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Azure.Messaging.ServiceBus.Amqp.AmqpSender.d__20.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Azure.Messaging.ServiceBus.ServiceBusSender.d__26.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Azure.Messaging.ServiceBus.ServiceBusSender.d__25.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Cpi.HoneyBee.DataAccess.Helpers.ServiceBusHelper.d__1.MoveNext() in C:\Users\rdowns\Source\HoneyBee\HoneyBee\Cpi.HoneyBee.DataAccess\Helpers\ServiceBusHelper.cs:line 34

@jsquire here's a minimal repro of some of our code. There is a commented out line because I've tried both; I wasn't sure if I could just pass an object (that is then converted into a Byte stream) or if it HAD to be a dynamic type before that conversion took place. The try-catch around the SendMessageAsync is just an effort to capture the error for this troubleshooting.
if (learnerCourse.EnrollmentID != null)
{
    //await _serviceBusHelper.SendMessageAsync("coursecompletion", new CourseCompletionRequest { UserId = learnerCourse.UserID, EnrollmentId = learnerCourse.EnrollmentID }, token);
    await _serviceBusHelper.SendMessageAsync("coursecompletion", JsonConvert.DeserializeObject<dynamic>(JsonConvert.SerializeObject(new CourseCompletionRequest { UserId = learnerCourse.UserID, EnrollmentId = learnerCourse.EnrollmentID })), token);
}

public interface IServiceBusHelper
{
    Task SendMessageAsync(string queueName, dynamic content, CancellationToken token);
}

public class ServiceBusHelper : IServiceBusHelper
{
    public ServiceBusHelper()
    {
    }

    public async Task SendMessageAsync(string queueName, dynamic content, CancellationToken token)
    {
        await using (ServiceBusClient client = new ServiceBusClient(ConfigurationManager.AppSettings["ServiceBusConnectionString"]))
        {
            byte[] contextByteStream = Encoding.ASCII.GetBytes(content.ToString());

            ServiceBusSender sender = client.CreateSender(queueName);

            ServiceBusMessage message = new ServiceBusMessage(contextByteStream);

            try
            {
                await sender.SendMessageAsync(message, token);
            }
            catch (Exception ex)
            {

            }
        }
    }
}

Thanks, @RyFive85.  Are you able to package that in a small console application that fails in the same way as your application?  Understanding references, versions, and any binding redirects that are defined will be helpful.  In the abstract, I'm not able to repro with the snippets.
Unrelated to the issue, I did want to mention a note form the snippet.  We'd recommend that you not create a new ServiceBusSender for each attempt to send a message.  For efficiency and performance, it would be better to create them once and cache/reuse unless you've got a very high number of queues that you're publishing to where the overhead would be prohibitive.  If you decide to keep creating the sender per-request, be sure that you close or dispose it.  By not doing so, the AMQP link that it uses is orphaned until it times out and the service force-disconnects it.   It also holds unmanaged resources that won't be cleaned up until the client is closed/disposed.

@jsquire for reasons that I'm unsure of, I built a console app using the same Framework version and C# version and it seemed to work. I tried removing the using around the Service Bus calls and that didn't work. I'm not sure where else to look to see what's different that isn't allowing this to flow.

It looks like I was able to revert the Azure.Messaging.ServiceBus package to version 7.0.0 and it worked. Not sure what the hang up is, but I guess that'll have to do for now.

I suspect that your application has some conflict in dependencies that is forcing a downgrade of the references used by the Service Bus package.   Normally when we're talking the .NET Framework, this comes from implicit binding redirects added either by another reference or a framework component directing something to the GAC.   In this case, I'm not sure exactly what we'd be looking for, but likely something related to System.Threading.Tasks.Extensions, Microsoft.Bcl.AsyncInterfaces, or System.Memory.Data.

@jsquire I checked all of the suggested dependencies and I have all the latest versions of all, unless the suggestion is might need an older version. I was able to determine that the break happens somewhere between version 7.2.1 (works) and 7.3.0 (doesn't work) of Azure.Messaging.ServiceBus.

It sounds like this could be due to the version of Microsoft.Azure.Amqp that is being pulled in. The Cancellation token support was added in 2.5.3, but it seems your reference is somehow being downgraded (as @jsquire hypothesized). Can you see what version is being used? Can you manually set the version to be the latest (2.5.10) and see if the issue persists?

@RyFive85:  Would you please be so kind as to share your main project file and any app.config-related assets?   I'd like to use them to try and reproduce locally.


Inconsistent AlignToPtr use

Getting the next opcode is sometimes done with PRENextOff(AlignToPtr(scan + REOpSz))^  and sometimes Inc(s, REOpSz + RENextOffSz)
It doesn't fail on many arch:
function AlignToPtr(const p: Pointer): Pointer; {$IFDEF InlineFuncs}inline;{$ENDIF}
begin
  {$IFDEF FPC_REQUIRES_PROPER_ALIGNMENT}
  Result := Align(p, SizeOf(Pointer));
  {$ELSE}
  Result := p;
  {$ENDIF}
end;

But compile on an arch that requires align, and it should fail

Correct note. But i don't have the hardware, so my fix will be blind, w/o tests... so I don't want to fix it.

Just remove the IFDEF.
Your intel/amd will not complain about the extra alignment.

@User4martin Will you help me with this issue, please? to do it you need to enable the $define here:
// Alexey T.: handling of that define FPC_REQUIRES_PROPER_ALIGNMENT was present even 15 years ago,
// but with it, we have failing of some RegEx tests, on ARM64 CPU.
// If I undefine FPC_REQUIRES_PROPER_ALIGNMENT, all tests run OK on ARM64 again.
{$undef FPC_REQUIRES_PROPER_ALIGNMENT}

Disclaimer: Someone with background on different CPU/arch should maybe double check some of my statements....

Well, right now, with that define enabled, it will fail on all platforms.
My understanding is that there are some CPU that can not access a longint unless it is 32 bit aligned (or a int64 unless it is 64bit aligned.)
Currently I would expect TRegExpr to fail on such CPU.
Code like
      OpKind_Char:
        begin
          Inc(ABuffer);
          N := PLongInt(ABuffer)^;

is likely to fail, because ABuffer may not be aligned.
It could also be that on some CPU such code runs slower, due to the non align (though then, its a gamble versus needing more cache lines).
Those CPU are probably mostly embedded/RISC. (Afaik they may cause an exception, if the address is not aligned / so I really am not sure)
So in order to know, if this define is needed after all => it would need to be tested on those cpu.
Afaik, fpc has a copy of this, does it have testcases? I would imagine the fpc team running there tests on various cpu.

As for the question if it may have a speed impact => maybe a CPU expert from the fpc team knows. (just testing is likely not revealing much, as things like cache hits may cause timings to vary to much.)

So first thing is to find out:

which target arch are currently broken (if any)
maybe, if it could have a speed impact (though I would defer that part)
If then fixing is urgent or not.

If it isn't urgent, more than half of the code that needs to be fixed could probably be replaced by code that doesn't need alignment on any architecture. (E.g. with a few exceptions the "next pointer" can be ReChar)

In either case, fixing the alignment code seems to be closer to rewriting it. So I wont be able to squeeze that in right now.

Let's suggest our new version to FPC bugtracker? who should do it: you / me?

if you would.


chore: cache parent module lookup

Currently, ingesting packages with a large amount of submodules and/or types can take a very long time.
For example, running the following:
const docs = await Documentation.forPackage('@cdktf/provider-aws@4.0.1');
console.time('render');
await docs.render({ language: Language.PYTHON, submodule: 'wafv2' });
console.timeEnd('render');

Will result in:
Installing package<EMAIL_ADDRESS>render: 9:52.761 (m:ss.mmm)

With this PR, by caching the parent module lookup, this is reduced to:
Installing package<EMAIL_ADDRESS>render: 32.382s

Some more analysis details. Before this PR, here is how the flamegraph looked like:

We can see the render method is taking the bulk amount of time compared to loadAssembly.
It also shows very noticeable hotspots
After this PR:

We can see render is now a small fraction of the cost, with no substantial hotspots on the call stack.
The hottest spot now is the validateSchema function of jsonschema.
@RomainMuller Do you think we can improve something there, or maybe run loadAssembly without validation? I don't think we need validation at this point, at least not where its used in construct hub.


Remove useless env MYSQL_PASS

Related to #19 .

I will follow the branch mattrayner/refactor so close this PR. New refactoring is been doing.


Action will stop working on 1st June 2023

I'm getting this warning:

Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Hi - has there been any progress on upgrading this action to run on node16 instead of node12? I looked through the releases but didn't see any mention of this. The listed due date is tomorrow. Thanks!

GitHub updated the blog post to say they're deferring the removal.


Error when sending news from 2nd location

I created a 2nd location for<EMAIL_ADDRESS>and changed the app id of the service identity afterwards.
There is an error when they try to send local news from their 2nd location: Insufficient budget.

There is an error when they try to send local news from their 2nd location: Insufficient budget.

Are they sending news from non-shop session?, this service has no budget!

yes, from non-shop session. I think the problem is that the code checks the app id of the default service identity, instead of the current service identity.

Still the insufficient budget error is normal.
I was about to ask, budget ordering/checking/updating...etc is done over the service user, it will be the same between different identities, this need to be changed, right? so every identity can order and consume the budget without affecting others?

That's true, but they were trying to send out local news from that identity, which doesn't require budget.

I think the problem is that the code checks the app id of the default service identity, instead of the current service identity.

no, it checks the default app id of the current service identity.
I just didn't notice it was a local news problem, sorry.
The problem is that the 2nd location identity has different app ids than the default one, and when loading the dashboard, if a customer is found, it just gets the app ids of that customer not the current service identity.


Formatting, embed, help text updates

A few housekeeping details:

User name formatting to exclude discriminator
Final coin display formatting
Join game embed made (hopefully) more clear
Help text updated
Unused function in utils/cringo.py removed.

I hope @williammck doesn't mind that I'm just pushing all this through. It's not bad code I promise!


fix: reset register panel state after successful registration

#134  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MasterPtato and the rest of your teammates on  Graphite


client: add application/atom+xml as valid MIME type

According to Microsoft, this is an acceptable MIME type for ODATA:
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-odata/8ee3b8ba-478c-49c1-992e-4e5ffdcd62fd
Some systems opt to use this kind of content header.

Codecov Report

Merging #194 (89ce7d1) into master (0599db2) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #194      +/-   ##
==========================================
- Coverage   92.66%   92.63%   -0.04%
==========================================
  Files           6        6
  Lines        2768     2768
==========================================
- Hits         2565     2564       -1
- Misses        203      204       +1

Impacted Files
Coverage Δ

pyodata/client.py
100.00% <100.00%> (ø)

pyodata/v2/model.py
93.26% <0.00%> (-0.06%)
:arrow_down:

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 0599db2...89ce7d1. Read the comment docs.

It is correct. However, could you please enhance the PR with also new test case for this new accepted MIME type?
E.g. def test_create_service_text_xml(metadata):
Also, update of CHANGELOG.md, under the Unreleased and "Fixed" section, would be nice.

Could you please rebase to the latest master (I don't like merge commits).

@OmniTroid I'd like to help this PR getting merged and therefore rebased this PR, added the missing test and a changelog entry: https://github.com/rettichschnidi/python-pyodata/tree/rs/upstream/extend-pr-194
@filak-sap, @phanak-sap Can you use it this way? Or is there another way I can help getting this PR merged?

I pushed the commits:

https://github.com/SAP/python-pyodata/commit/b678d0a19cc032e932f2ae259675d50262317c0e
https://github.com/SAP/python-pyodata/commit/b5b0b4086138435658740ec6629f796fbf3f7ce9

Thank you!


Fix ViewList/applyNodes

Such code is for placeholder now. There are multi variant of the protocol. (OS_RELEASE_2021 / OS_RELEASE_2024)
The original code is for OS_RELEASE_2021 and yours is OS_RELEASE_2024.
Part of the code is aligned with OS_RELEASE_2021, part is OS_RELEASE_2021 and some even support both by #if macro.
So this is the expected behavior.
If you want to contribute to this project, I suggest starting from searching and fixing the FIXMEs in the codebase or improving the test case coverage which would more likely to be merged.


Warning/filtering for trusted markets

Dispute mechanism is now optional which means that the market will be resolved as soon as it's reported. We won't surface this as an option on the front end by we should warn or filter out markets without a dispute mechanism

Put an icon at the end of here:

Filter out markets that are trusted and not created by an address in our white list


When power toys is activated, it repeatedly lights up even when the display is off.

Microsoft PowerToys version
0.70.1
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
Leave the computer unattended and automatically turn off the display.
✔ Expected Behavior
The display is not illuminated by POWER TOYS.
❌ Actual Behavior
Display lights up repeatedly
Other Software
No response

Is this happening on 70.1?  /reportbug for settings. This bug should be fix if you have MWB enabled

PowerToysReport_2023-06-02-15-14-50.zip
MWB is enabled but not fixed.


Unable to process multiple preparations refering to the same sequencing run

This refers to jobs:

490c4831-33c6-44a2-8a34-ddcf08d0c40d
a78aa38d-5b82-4137-9950-8524414c4b51
b9b6b094-3345-4808-80dc-7a4488abdb4f

In this situation, replicate samples were sequenced on the same lane. To account for this, and to ensure unique samples exist in the preparation, each set of replicates had its own sample sheet. Processing on the three sample sheets occurred in parallel. What appears to have happened is that the processing jobs all attempted to move the same files (relative to uploads/) to different locations at preparation creation.
It is important to note that the Qiita processing pipeline remarked these jobs as successful, even though the constructed preparations were unsuccessful.

From another perspective, three QPP jobs were submitted using the same run-id (230411_M05314_0358_000000000-KYF72) and lane number (1), w/mapping-files containing an identical set of sample-names but with differing values for barcode, primer_plate, well_id, sample_plate, project_name, orig_name, and well_description.
The following three sets of items get moved into the uploads directory:
A 'BLANKs' file: 230411_M05314_0358_000000000-KYF72_Ornish_PMRI_FOBT_Rep_3_10317_blanks.tsv
the final set of fastq files: QCJob/Ornish_PMRI_FOBT_Rep_3_10317/amplicon/*
One or more prep-information files, depending on the number of projects in the mapping-file/sample-sheet: 230411_M05314_0358_000000000-KYF72.Ornish_PMRI_FOBT_Rep_3_10317.1.tsv
In this case, the blanks and prep-information filenames are unique across the three jobs (Rep_1, Rep_2, Rep_3), so they shouldn't overwrite each other. However as their filenames are built using metadata supplied by the user, this is not always true.
The three jobs were also ingesting their set of prep-information files and updating the set of BLANKs in Qiita within the same time frame.

(FYI) Our use-case for being able to start a QPP job on a run-id that was already processed was to overwrite previous results w/improved ones. This is still a valuable use-case and why overwriting data in the uploads directory was allowed originally.
In the short term, running each job sequentially is the best option to avoid overwrites and unpredictable behavior. We end up processing the same BCL files more than once which is waste, but in this case the final fastq output isn't large by our standards (~4.7GB). It'll be faster to process them sequentially than to hack a short-term solution.
In the long term, submitting multiple jobs, one for each prep is generally wasteful as the two most resource-intensive steps in a QPP job (bcl->fastq conversion, adapter-trimming & human-filtering) are being performed once for each prep instead of sharing the same results. Instead we should make a small modification to the UI and the pipeline to accept multiple pre-prep files at the same time. QPP will then reuse the results of the most resource-intensive steps across all preps. We can introduce a lock on the run-id (alternatively the run-directory itself) and return an error if a user tries to submit a new job using a run-id that is currently being processed. This will prevent the unpredictable behavior from happening again.
There will be some slight changes to the layout of the final output folder to accommodate multiple preps and the copy commands in addition to some code changes to perform multiple FastQC and MultiQC operations, one against each prep.

Thanks @charles-cowart, this seems reasonable. And agree some notion of a lock would be valuable if the output filepaths are not assured to be unique to a processing job.

Hi Charlie, are there any updates on this issue?

@wasade No updates on this issue. I'd like to run them by @antgonza first.

Addressed by https://github.com/biocore/mg-scripts/pull/104

run_dir locking is likely not needed since SPP no longer directly moves files into Qiita's uploads directory. However I am still looking into being able to submit multiple pre-prep files to a pipeline in order to make use of the same bcl->fastq and potential QC steps.

Discussed with Rodolfo and Antonio and we agreed that the only time submitting multiple preps would be needed is to support replicates. Since plate-level replication has now been implemented (but not yet deployed to production), multiple submissions are no longer needed and this issue can be closed.


Infrastructure automation with Ansible

Added ansible playbooks to perform the following:

Provision EC2 resources
Deploy the relay chain
Deploy the parachain

Details:

Relay chain

Simple 2 node setup (alice & bob). On t3.medium instances
RPC url is wss://rococo-rpc.snowfork.network (SSL certs issued by LetsEncrypt)

Parachain

2 collator nodes, on t3.medium instances.
RPC url is wss://parachain-rpc.snowfork.network (SSL certs issued by LetsEncrypt)

Chain security: Not much. The relay chain supports Sudo access with the built-in Alice account. The parachain also accepts relayed messages from our builtin //Relay account seed. But this is just for testing, we're going to ditch our relay chain when we integrate with the actual Rococo chain.

i don't know ansible so can't easily review, but given its just for our testnet, if it works, then that's review enough :)
Also, we discussed it a few months ago I think but it may be worth skimming through https://github.com/gantree-io/gantree-lib-nodejs again to see if it is useful for us, or if there is some ansible code we can copy/reuse. I'm not sure how active it is anymore but if it looks useful/relevant for us, i can reach out to their team to get updates.

i don't know ansible so can't easily review, but given its just for our testnet, if it works, then that's review enough :)
Also, we discussed it a few months ago I think but it may be worth skimming through https://github.com/gantree-io/gantree-lib-nodejs again to see if it is useful for us, or if there is some ansible code we can copy/reuse. I'm not sure how active it is anymore but if it looks useful/relevant for us, i can reach out to their team to get updates.

Ah yeah, I forgot about that. Looked over their Ansible code, and there is some stuff we could definitely reuse as we improve our testnet (hardening, robustness, security, etc).


Correctly pass index in getItemProps

Per discussion in #4, this changes the type of itemPropsOptions to pass index as a Nullable int, and then adds a new implementation for getItemProps that allows the user to optionally pass index.

This is released as 0.1.1.
Let me know if you encounter any more issues.
PS: I'm pinging now downshift dep to a specific version to ensure compatibility with the original library. As new feature and versions will come out we'll update the bindings accordingly. Hope that makes sense 😉


UN-16X: Refactor Insights page blocks

Resolves:

https://national-archives.atlassian.net/browse/UN-163
https://national-archives.atlassian.net/browse/UN-164
https://national-archives.atlassian.net/browse/UN-162

Also changes the overall approach to content on Insights pages:

'Section' is the only valid block option at the top-level, which has a required 'heading' value that always renders as a
.
'Sub-section' can be added to a 'Section' to nest content even further, which has a required 'heading' that always renders as a
.
Any block added to a 'Section' that has a 'heading' will automatically use a

Any block added to a 'Sub-section' that has a 'heading' automatically use a

Any sub-blocks of these auto-adjusting content blocks should automatically use the correct heading tag too (one level higher than the parent)

Included data migration to migrate existing content to new structure - However, due to the limitation of the current blocks, there are cases where invalid use of
 headings will change the order of content slightly. Realistically though, this is as good as it's going to get! All content will be revisited anyway - we just didn't want to lose everything entirely.

@AshTNA would you be okay to review this?

On testing: What is it that we actually want to test? The base blocks and standard page editor interface are already tested by Wagtail. Maybe there's an argument for testing that the get_context_data() overrides behave as expected, but other than that, there's not really anything 'Custom' going on here. Testing that configurations of blocks work properly is a bit like testing built-in Django model fields:

They behave according to how you configure them
You follow documented APIs at the time of configuring
If that API changes, Wagtail mention it in the release notes and bump the version to account for it
When you upgrade to the next version, you review the release notes and search for relevant code at that time
Things are very often 'deprecated' for a couple of versions before support is completely removed too, so you upgrade one version at a time and look out for warnings.

Thanks  @AshTNA @ababic for this info. I was not sure if those new blocks required test cases or not as its just new code added or as I understand now configured in this case.

Hi @AshTNA, @ababic
Thanks for this 👍 Just a few things:

As @AshTNA mentions, we’ll need the data-controlled-by attribute on the .section-content rather than .section-wrapper.

There’s a data-section-level attribute on .section-wrapper elements; what’s this used for?

I believe we’d only need id’s on h2 elements as that’s what the in-page nav links will use to jump to the relevant section. Id’s won’t be required on any other headings I don’t think.

There’s a data-section-level attribute on .section-wrapper elements; what’s this used for?

It's available in the template context, so thought it might be useful for targeting content of a specific level (for whatever reason). Also useful for debugging :)

I believe we’d only need id’s on h2 elements as that’s what the in-page nav links will use to jump to the relevant section. Id’s won’t be required on any other headings I don’t think.

The sections and other elements all extend from a base block that makes them aware of the content depth and makes these values available in the context. The IDs are added to all h3s too simply because the same template is used for sections and sub-sections. If it is a problem that the ids are set for sub-section heading too, It's entirely possible to put a condition around that output in the template. But, if not, it simply doesn't make sense to complicate the template with unnecessary conditional.

Okay, let's leave the headings as they are then.


Make Object.hashAll and Object.hashAllUnordered accept nullable lists

Unlike Object.hash, Object.hashAll and Object.hashAllUnordered does not accept nullable parameters, which it should to make it consistent with Object.hash and flutter's (soon-to-be previous) hash function (hashList).

I disagree with doing this change.
It's not consistent with Object.hash. The Object.hash function accepts a single object, which may be null (because null is an object).
The Object.hashAll accepts zero or more objects, as a list. The list elements can be null. Making the list be null does not match that. it's unnecessary.
There is no advantage in allowing you to pass in null, because you can just not call the function at all if you have a null value.
If you have a potentially null list value, and want to hash it, just do Object.hashAll(maybeList ?? const []), or make a helper function:
int myHashAll(List<Object?>? maybeList) => maybeList == null ? null.hashCode : Object.hashAll(maybeList);

You can then use that if you need it, but not if you have a non-null list.
If we make Object.hashAll accept null as argument, even though it doesn't need it, that can hide mistakes in the program, where a value is null unexpectedly. You won't get any help discovering such a bug.
Example:
int something(Object x) {
  List<Object?>? collection;
  if (x is SpecialThing) {
    // Always true, I almost promise!
    collection = x.listOfStuff;
  }
  // some more code here.
  return Object.hashAll(collection);
}

This code will get a warning now, because collection is potentially null.
If Object.hashAll accepted null, you wouldn't get that warning.
So, I'm firmly against allowing hashAll to accept null. It's bad design.
Even if we had introduced the functions prior to Null Safety, I'd still have made them throw on a null argument.

@lrhn I would be curious to have you review the PR above that migrates Flutter to this new API. There's a number of places where we're being forced to add ?? <Object>[] which seems really quite unfortunate and not at all obvious, and I wonder if you think they represent places where we've made poor API design decisions that we should rethink.

(If you have any advice on how we should implement the dart fix given the API difference that would be useful too.)

If it was me, I'd probably use ?? const<Object>[] to avoid allocation (but risk polymorphism, at least if Object.hashAll is inlined - if not, it's almost certainly polymorphic already), or I'd use c == null ? 3513 : Object.hashAll(c) if the expression is a variable already.
Not allowing null makes it slightly harder to use when you have either no list or a (probably potentially empty) list, but that itself is something I'd try to avoid too. Is there a logical difference between no list and an empty list?
If not, don't have two states for the same thing.
If yes, you probably want different hash codes for the two states.
The meaning of null in this context is part of the caller's domain logic, the Object.hashAll function cannot know what it means, it can only choose to ignore it. If anything, it should return null on a null argument, so you can see it happened, and handle it. That would make the return type int? which would annoy every other user of the function. Better to stick to the one job it has: Hash a sequence (iterable) of values.
Not allowing null is safer than allowing null for an operation which doesn't need to handle null. It won't hide accidental uses of nullable variables. It avoids assigning a specific meaning to a value outside of the domain that the hashAll function is actually defined on.

Fair enough. I think that's more theoretically right than pragmatically right but I can respect the reasoning.


Fix up readme codeblock indentation

Actually I just noticed you use the current form of indentation on all of the projects (that I saw). I'm not sure why, but you do your thing. Sorry for the inconvenience.


Update debugger.md for rc2

This PR should be completed once we release the RC2 version of the extension
This checkin updates debugger.md for RC2.

Hi @gregg-miskelly, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

Looks like you need to sign a CLA @gregg-miskelly. Possibly because you haven't joined the .NET Foundation organization?

I actually am in the .NET Foundation, but I don't remember if I signed the CLA yet.

The bot says no :smile:

@gregg-miskelly, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

@gregg-miskelly Is 0.3.7 the RC2 version of the extension?

Nope -- grab the latest from https://github.com/OmniSharp/omnisharp-vscode/releases for the RC2 version.

See http://aka.ms/vscclrdogfood for complete instructions if you want to try recent builds of the CLI before they ship.

@gregg-miskelly While I can now debug a netcoreapp1.0 with RC2 bits, I can no longer debug a netstandardapp1.5 with RC3 bits using 1.0.3-rc2 of this extension; the latter fails with the usual no CoreCLR events raised error.

:smile:


⚠ Fortnite has degraded performance

In 761c784, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1693 ms

Resolved: Fortnite performance has improved in 46bbab9.


Secure SAML implementation issue.

We need to implement SAML based secure authentication. Our IDP will be Okta and OneLogin. We use the following strategy configuration at SP side for Okta-
var oktaLoginStrategy = {
host: 'http://localhost:3000',
path: '/login/callback',
realm: 'urn:node:app',
entryPoint: "https://dev-528399.oktapreview.com/app/builtiodev528399_oktasp1_1/exkbbi8vwj2OsHjbE0h7/sso/saml",
issuer: "http://www.okta.com/exkbbi8vwj2OsHjbE0h7",
additionalParams: {
'RelayState': "test"
},
signatureAlgorithm: 'sha256',
decryptionPvk: privateKey,
privateCert: privateKey,
cert: oktaPublicKey,
identifierFormat: 'urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress'
};
and for OneLogin we use-
var oneLoginStrategy = {
host: 'http://localhost:3000',
path: '/login/callback',
realm: 'urn:node:app',
entryPoint: "https://flow-dev.onelogin.com/trust/saml2/http-post/sso/686218",
issuer: "https://app.onelogin.com/saml/metadata/686218",
additionalParams: {
'RelayState': "test"
},
signatureAlgorithm: 'sha256',
decryptionPvk: privateKey,
privateCert: privateKey,
cert: oneLoginPublicKey,
validateInResponseTo: true,
identifierFormat: 'urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress'
};
But for Okta it is giving error as "Cannot read property 'getAttribute' of undefined" and for OneLogin it is giving error as "Invalid signature". Further, we debugged into the module and found that for Okta it breaks while finding algorithm and for OneLogin, it able to decrypt 'CipherData' but it breaks while validating the signature.
Our private key format is-
-----BEGIN PRIVATE KEY-----
-----END PRIVATE KEY-----
Please help us into this.

This appears be a support request, which we don't have the resources to answer here. If you believe you've found a bug in passport-saml, please open a bug report, preferably with an update to the test suite which provides a failing test to demonstrate the bug, and ideally with a fix for the bug as well.

@ambermore have you found the solution for problem : "Cannot read property 'getAttribute' of undefined" ?
I am also facing the same issue.

Issue resolved, As I was using older version of passport-saml. So i updated version in package.json file.


listen not working anymore

The login works, I can send messages and retrieve friends, but receiving messages while listening is not firing the on_message method. Am I doing something wrong?
client = Client(username, password)
client.listen()

in parseMessage the content coming in is always {u'reason': 110, u't': u'refresh', u'seq': 0} and therefore on_message is never fired.
I googled a bit and I found https://github.com/defaultnamehere/zzzzz/issues/25
Someone here thinks getting new cookies will help.

Check issue #45, have you added that "clientid" line?

oh. sweet. Added it.. it worked. Dunno how I missed that.


tests: Move CI from Travis to GitHub Actions.

This configuration is equivalent, except that Ubuntu and Java are updated to the latest LTS releases.
Fixes: #4174

Excellent, thanks!
I don't see results from it shown here on this PR thread. Perhaps the workflow needs to exist on a branch in the repo itself? I'll go read some of the docs, and experiment with pushing this commit to a branch here.

Excellent, thanks!
I don't see results from it shown here on this PR thread. Perhaps the workflow needs to exist on a branch in the repo itself? I'll go read some of the docs, and experiment with pushing this commit to a branch here.

... Ha, OK! I:

pushed the exact same commit to a branch within this repo;
made a dupe PR from it, #4384;
and that seems to cause the action to start both on that PR and this one!

In fact it looks like two of them: one for having pushed to a branch, and one for having made a PR from that branch.
I guess because it's the same commit, it's probably showing the same runs' results on both PRs.

... Ha, OK! I:

pushed the exact same commit to a branch within this repo;
made a dupe PR from it, #4384;
and that seems to cause the action to start both on that PR and this one!

In fact it looks like two of them: one for having pushed to a branch, and one for having made a PR from that branch.
I guess because it's the same commit, it's probably showing the same runs' results on both PRs.

The (push) runs against the latest ref from the branch, and the (pull_request) runs against a trial merge into the base of the PR. This article explains in more detail.

The (push) runs against the latest ref from the branch, and the (pull_request) runs against a trial merge into the base of the PR. This article explains in more detail.

The (push) runs against the latest ref from the branch, and the (pull_request) runs against a trial merge into the base of the PR. This article explains in more detail.

Ah, good to know.
In our usual workflow we don't push to branches here -- we each push feature branches to our respective personal forks and send those as PRs. So I think that means that typically push won't run on a PR, only pull_request, and push will run when there's a push to master (the only branch we routinely push to.)

The (push) runs against the latest ref from the branch, and the (pull_request) runs against a trial merge into the base of the PR. This article explains in more detail.

Ah, good to know.
In our usual workflow we don't push to branches here -- we each push feature branches to our respective personal forks and send those as PRs. So I think that means that typically push won't run on a PR, only pull_request, and push will run when there's a push to master (the only branch we routinely push to.)

After the small changes discussed above and after we merge this, If you're interested, I think there's a couple of followups this opens up that would potentially make the CI significantly faster and nicer than it's ever previously been:

Cache node_modules, to save a good chunk of the time.
Split into several jobs that run in parallel (and call tools/test with specific suite names to do different parts of the tests), to make it faster still.

Probably these would all depend on a common initial job that does yarn install and saves to the aforementioned cache.

Persuade Flow to stop spewing "Please wait. Server is initializing (parsed files 30000)" messages, and persuade Jest and Flow and other tools to use color.

This would probably involve adding an option like --ci to tools/test and passing it here. Then each suite in tools/test would pass the appropriate options to tell the respective underlying tool what to do.
It'd replace the TERM=dumb, which is a bit of a crude solution explained in 661438435f82647653dfb53a78594fe4e98171fe for getting Gradle to stop spewing something a lot like that Flow spew. That TERM=dumb is likely the reason Jest isn't showing color; and on the other hand Flow didn't take the hint.

Get the fancy log grouping like some of the upstream actions do, with ⯈/⯆ expandos. It looks like they do this with calls like core.startGroup('Running foo'), using the NPM package @actions/core. ... And looking at that function's implementation (1, 2), I think that boils down to echo "::group::Running foo". (With a bit of percent-encoding in case the message contains newlines.)

This might not be relevant if we end up splitting the tools/test run completely into separate jobs. Or for that matter we could split it into separate steps, which might also make this irrelevant. Well, it was entertaining for me to dig into just now. :slightly_smiling_face:

After the small changes discussed above and after we merge this, If you're interested, I think there's a couple of followups this opens up that would potentially make the CI significantly faster and nicer than it's ever previously been:

Cache node_modules, to save a good chunk of the time.
Split into several jobs that run in parallel (and call tools/test with specific suite names to do different parts of the tests), to make it faster still.

Probably these would all depend on a common initial job that does yarn install and saves to the aforementioned cache.

Persuade Flow to stop spewing "Please wait. Server is initializing (parsed files 30000)" messages, and persuade Jest and Flow and other tools to use color.

This would probably involve adding an option like --ci to tools/test and passing it here. Then each suite in tools/test would pass the appropriate options to tell the respective underlying tool what to do.
It'd replace the TERM=dumb, which is a bit of a crude solution explained in 661438435f82647653dfb53a78594fe4e98171fe for getting Gradle to stop spewing something a lot like that Flow spew. That TERM=dumb is likely the reason Jest isn't showing color; and on the other hand Flow didn't take the hint.

Get the fancy log grouping like some of the upstream actions do, with ⯈/⯆ expandos. It looks like they do this with calls like core.startGroup('Running foo'), using the NPM package @actions/core. ... And looking at that function's implementation (1, 2), I think that boils down to echo "::group::Running foo". (With a bit of percent-encoding in case the message contains newlines.)

This might not be relevant if we end up splitting the tools/test run completely into separate jobs. Or for that matter we could split it into separate steps, which might also make this irrelevant. Well, it was entertaining for me to dig into just now. :slightly_smiling_face:

Thanks for the detailed review!

Cache node_modules, to save a good chunk of the time.

The npm-install action already does this.

Thanks for the detailed review!

Cache node_modules, to save a good chunk of the time.

The npm-install action already does this.

And merged :tada: -- thanks!
I made some small whitespace changes, and small edits to the commit message -- mostly just wrapping it to within 70 columns.

And merged :tada: -- thanks!
I made some small whitespace changes, and small edits to the commit message -- mostly just wrapping it to within 70 columns.

Cache node_modules, to save a good chunk of the time.

The npm-install action already does this.

Hmm! That'd make sense, but... it looks like that step took 1m29s on the run after your update. That's about as long as it was on the previous revision (1m35s), and seems like long enough to install the node_modules from scratch.
Maybe the cache will only work after there's a version in master? I guess we'll find out. If it continues to not benefit from caching, then I guess we'll want to debug.

Cache node_modules, to save a good chunk of the time.

The npm-install action already does this.

Hmm! That'd make sense, but... it looks like that step took 1m29s on the run after your update. That's about as long as it was on the previous revision (1m35s), and seems like long enough to install the node_modules from scratch.
Maybe the cache will only work after there's a version in master? I guess we'll find out. If it continues to not benefit from caching, then I guess we'll want to debug.


Postponed annotation evaluation breaks Annotated when used alongside Info

Describe the Bug
The following will throw TypeError: Query fields cannot be resolved. Unexpected type 'typing.Annotated[int, <strawberry.arguments.StrawberryArgumentAnnotation object at 0x7f55080339d0>]'
from __future__ import annotations

from typing import Any

import strawberry
from strawberry import field
from strawberry.fastapi import BaseContext
from typing_extensions import Annotated

class Ctx(BaseContext):

    def __init__(self) -> None:
        super().__init__()

Info = strawberry.types.Info[Ctx, Any]

@strawberry.type
class Tmp:
    id: int
    name: str

@strawberry.type
class Query:

    @field(description="Get Tmp by id.")  # type: ignore
    async def tmp(
        self,
        info: Info,
        id_: Annotated[
            int, strawberry.argument(name="id", description="The ID of the Tmp")
        ],
        name: str,
    ) -> Tmp:
        return Tmp(id=id_, name=name)

Schema = strawberry.Schema(Query)

Commenting out
from __future__ import annotations

or
        info: Info,

allows the schema to generate successfully.
System Information

Operating system: Ubuntu 20.04.5 LTS
Strawberry version (if applicable): Tried 0.158.2 and 0.159.0

Additional Context
This same error was seen in #1819, but the root cause here seems to be different.
Adding types that weren't related to Info seemed to not be problematic (such as the non-Annotated name argument). Using Info[Any, Any] exhibits the same error (so it doesn't seem to be specific to the empty Ctx).
PYTHON_VERSION=3.10.10

this might be fixed by: https://github.com/strawberry-graphql/strawberry/pull/2592

https://github.com/strawberry-graphql/strawberry/pull/2592 got merged. Upgrading your strawberry dependency to 0.165.0 should fix the issue :)


Fix isAuthenticated method

The old isAuthenticated method was requesting the AuthSession.get (which redirects to login if you're not authenticated)

Closing, since the changes has been merged already by #782


Bump pip:pillow to version 9.3.0

Resolve dependabot alerts:

https://github.com/coda/packs-sdk/security/dependabot/23 (CVE-2022-45199)
https://github.com/coda/packs-sdk/security/dependabot/24 (CVE-2022-45199)

@coda/infosec @jonathan-codaio

It looks like MkDocs has a direct dependency on importlib_metadata:
https://github.com/mkdocs/mkdocs/blob/56b235a8ad43f2300d17f87e6fa4de7a3d764397/pyproject.toml#LL43-L43C57
Not sure why it got pruned from Pipfile.lock.

Hoping that explicitly pulling in importlib_metadata will fix it. Should it go under dev packages instead?

I guess putting it in the same section as mkdocs is logical, so seems fine where you have it.


Tab Transitions

Maybe add smoother transition between tabs, like a reverse scroll kind of thing...
Like when a user clicks tab two (from tab one) the line under one moves to two and the content appears to be coming from 3?
Best,
Jake

This has been fixed in https://github.com/Daemonite/material/commit/c5a30ab9e735b341df946c28baa3070f501d3fe4


Cant access DL ASE Preview, even after adding account on botbuilder.myget.org

I have created an account on botbuilder.myget.org and logged in.
When I try to access the link given in the article, I get "You are not allowed to access this feed."
What do I need to do to get access the the ASE preview?

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

ID: c463a003-c709-b516-ce1b-6c45537de3b2
Version Independent ID: 8ca42668-23ac-6dca-054d-d183b0fb5b0b
Content: Create .NET client to connect to direct line app service extension - Bot Service
Content Source: articles/bot-service-channel-directline-extension-net-client.md
Service: bot-service
GitHub Login: @Kaiqb
Microsoft Alias: kamrani

@DarrenThurman The feed is now public. There were a few packages that got merged into the main SDK and the whole experimental feed was mistakenly closed instead of just a few packages.


typescript-specific docs?

any plans on writing docs for typescript usage? looking through the source i can't figure out how to explicitly type things. if it's not implemented yet, i suggest something like what kysely https://github.com/koskimas/kysely does

I don't think this is necessary and will just clutter the documentation.
Your editor LSP and autocomplention should be enough to guide you which types are available or returned.


Drawing on image

XamarinPainter can load an image into its canvas, but we need to make the posibility that XamarinPainter can only paint on the image and not on the whole canvas.

Fixed in 0.1.11-beta


Turn left

This issue was reformulated later in the meeting, and we didn't know how to delete it.

You can just close it and mention why you did so.


Showing different status on Home page and Security & Privacy page.

Showing me complete even when there are many issues in the Levels. Even primary device is not confirmed. The overall status is not a different value, it is always derived from the level statuses, which are derived from the RK statuses. So the only persistent values across sessions is the RK status. When RK status changes, it forces the Level status and the overall status to be recalculated and rerendered.

Verified this issue on dev app v2.0.01(374)


Make "esy shell" an alias to "esy $SHELL" add "esy pure-shell"

Right now esy shell is a almost-"pure" shell (almost same env which is used for sandboxed builds). That purity isn't what a user expects when running own commands but something which is valuable when debugging a broken build.
Instead what we should do:

esy shell is an alias to esy $SHELL and see #7 for improvements there.
esy pure-shell command is a "pure" shell — it should be exactly the same env which is used for building a package.

Same should be done regarding to esy CMD — it should run CMD in a non-pure shell, with user customizations enabled.

In the mean time, since esy CMD scrubs the environment so cleanly, vim will fail, and here's the current workaround:
esy env SHELL=$SHELL && vim


field writer's always generic

Alternative to #621
Reverts 760670616ed807041767cade52518291c810177c
Advantages:

easier generation logic, identical for single fields and field arrays (less potential bugs)
easier to integrate #612
less boilerplate, faster compilation

Disadvantages:

as writer not attached to offsets, not obvious meaning of writer
bigger firmware in debug mode? (need check)

r? @adamgreig
(rust-highfive has picked a reviewer for you, use r? to override)

@newAM Could you test this one also?

I prefer this. Does this increase size considerably in non-opt profile?

I prefer this. Does this increase size considerably in non-opt profile?

Tried one of my test binaries, opt-level 0.  98k with svd2rust 0.24.0, 98k with this PR.  No change on opt-level 1 either.

0.24 is broken. It makes sense to compare only patched versions. But sounds good anyway.
@Emilgardis Let's merge this one then.

bors r+


Add itertools.cycle() and itertools.chain.from_iterable()

I think the only thing left is combinations_with_replacement re: https://github.com/RustPython/RustPython/issues/1361

Nice work!


Fixing issue with bit allocation byteoffset calculation

The byteoffset calculation was skewed to double include the offset value calculated. The double calculation happens if the starting ordinal is part of the head sequence block. This error in calculation could result in duplicate but getting allocated eventually propogating to ipam and vni id allocations
Signed-off-by: Abhinandan Prativadi<EMAIL_ADDRESS>

Thank you for finding this. I think this issue would affect the --ip-range use case.
Please consider this change instead:
diff --git a/bitseq/sequence.go b/bitseq/sequence.go
index 86cf69b..6319f15 100644
--- a/bitseq/sequence.go
+++ b/bitseq/sequence.go
@@ -505,6 +505,7 @@ func getFirstAvailable(head *sequence, start uint64) (uint64, uint64, error) {
                }
                // Moving to next block: Reset bit offset.
                bitOffset = 0
+               byteOffset = 0
                byteOffset += current.count * blockBytes
                current = current.next
        }

By the nature of the rle bitsequence, we will iterate the for loop at most once. Because if current.block == blockMAX, then current.next.block != blockMAX, it cannot be otherwise.
Also, we already have a test function specifically for getFirstAvailable.
Please consider enhancing it (in addition to your new test) controlling the start field in the input array list:
--- a/bitseq/sequence_test.go
+++ b/bitseq/sequence_test.go
@@ -155,44 +155,50 @@ func TestSequenceCopy(t *testing.T) {
 func TestGetFirstAvailable(t *testing.T) {
        input := []struct {
                mask    *sequence
+               start uint64
                bytePos uint64
                bitPos  uint64
        }{

So in addition to the current input slice elements, please add few counterparts for each with  start != 0 (and same expected bytePos and bitPos)

Thanks @aboch for taking time to review it. I will incorporate the changes.


feat(tools): Flex and Spacer components - UI Components

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the main branch of freeCodeCamp.
[X] I have tested these changes either locally on my machine, or GitPod.

This is related to issue #44668
Clear part of Chapter components https://github.com/freeCodeCamp/chapter/issues/1143

Can you delete client/core.3149 file from the commit? these aren't needed in the repo

Just did! Let me know if there is anything else to be done.

:sparkles: :sparkles: AWESOME! :sparkles: :sparkles:
LGTM.
Thanks for this pull request and for contributing to the codebase for the first time. We will be looking forward to more contributions in the future.
Happy contributing.

Thanks for the pull request.
We are focusing on completing the https://github.com/freeCodeCamp/freeCodeCamp/issues/44668 requirements list for the first phase of the component library.
If you are still interested in contributing to component library, I suggest developing to the remaining components on the list first.
Note: the component library will be used in Chapter. As a result, building any component count as contributing to Chapter.


LVGL Example for ESP-IDF 5.1.1

LVGL Example for ESP-IDF 5.1.1

Hi @nfoliveira-foli ,
Thanks for submitting the PR, much appreciated. But looking through it, there is too many files for what will probably end up being a relatively niche section. I just don't think it makes sense for everyone who is pulling this repo to be pulling down an additional 600 files for an IDF example.
Would you have any interest in creating a "CYD IDF Examples" repo that we could link to from here?

Hey Guys
Sorry for long delay.... so it was the first time that I did this web example of LVGL works on ESP-IDF version 5.1.1, but yeah it's horrible and using the version LVGL 7.and I  needed to change a couple of file references, so wasn't impossible to use the current lib.
Now I 've finally could make a new example with version LVGL 8.3.10 and TTFT_eSPI work fine in CYD but using arduino IDE.
I really need to pass it to ESP-IDF without all these files, but I need some free time.
Thank so much
Best regards


Any way to link an existing GCE instance when doing vagrant up?

Is there a way to link to a previously created  instance instead when running vagrant up? I created an instance, and after deleting that folder I've lost the ability to connect with it with vagrant ssh.

Hi @enriquetuya!
No, there's no such functionality since this workflow is not really covered by vagrant.
However, if you've just deleted .vagrant folder it should be somewhat easy to restore state by just cross-referencing it with ~/.vagrant.d/ folder, since the local .vagrant folder stores just a couple of id's in case of cloud vm's.
Hope it helps!

I'm closing this issue since this looks resolved.
However, if you still have any questions - no worries at all - just reopen and I'll help you right out!


[MRG] Rebase MEAN stack on the updated jsPsych fork

I fixed the trigger discrepancy we had. Now, the trigger argument to add is always singular. Also, now the trigger doesn't have to be declared in order for the other experiments to work.
Also, I added an auto-browser launcher when node server.js is invoked. If you don't like it, I can drop that commit.

closed for https://github.com/OpenBCI/OpenEXP/pull/7


Log Broken with Bar

should fix by either fixing min for log scale at 1   or must set x/y value to the min value of the scale (is there a way to do that in vega?)

use domainMin or clip:true for now?


The javascript viewer of Draw IO does not comply with Salesforce JavaScript Strict Mode Enforcement

[ Y] I agree to follow the Code of Conduct that this project adheres to.
[ Y] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
As mentioned in the title we want to integrate DrawIO viewer with Salesforce but the javascript viewer of Draw IO does not comply with Salesforce JavaScript Strict Mode Enforcement. You can test this yourself with https://developer.salesforce.com/docs/component-library/tools/locker-service-console
Can you fix this?
Kind regards,
Mario

Please provide a link where we can see what the actual problem is.

"Error: assignment to undeclared variable mxForceIncludes"
that?

Yes that. And when you "fix" this the next Error: xxx is not defined will popup.

OK. That's too much work. I would suggest to fork the project and fix the errors specifically for salesforce.


Output consensus sequence for a POA graph

Implement the HeaviestBundle algorithm described in Lee et al. (2003) to generate consensus sequences for a POA graph.
Can also be used to obtain RNA isoforms.

Hello,
I was looking at this crate because the techniques described sounded interesting.  I did some preliminary exploration of the code to see if any consensus functionality was implemented and stumbled upon this open issue.  Is this still on the TODO list?  I was hoping to compare the method to some others to see how it did in that application space.
Thanks,
Matt

It's still on the TODO list, indeed. It will be one of my higher priorities after I submit my thesis!


Client Segfault

$ gdb --args ./dnscat --host <IP_ADDRESS> foobar.com
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
http://bugs.launchpad.net/gdb-linaro/...
Reading symbols from /home/user/dnscat2/client/dnscat...done.
(gdb) run
Starting program: /home/user/dnscat2/client/dnscat --host <IP_ADDRESS> foobar.com
[[ WARNING ]] :: INPUT: Command
[[ WARNING ]] :: Session successfully created: 22552
[[ WARNING ]] :: Session creation request
[[ WARNING ]] :: Setting config: max_packet_length => 109
[[ WARNING ]] :: OUTPUT: DNS tunnel to foobar.com
Got a command: COMMAND_PING [request] :: request_id: 0x0001 :: data: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Got a ping request! Responding!
Response: COMMAND_PING [response] :: request_id: 0x0001 :: data: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Program received signal SIGSEGV, Segmentation fault.
handle_message (message=<error reading variable: Cannot access memory at address 0x7ffeffffffe8>,
message@entry=<error reading variable: Cannot access memory at address 0x7fff00000008>,
d=<error reading variable: Cannot access memory at address 0x7ffeffffffe0>,
d@entry=<error reading variable: Cannot access memory at address 0x7fff00000008>)
at driver_command.c:137
137     }

I used to be able to repro 100% of the time on my work computer. Then I didn't touch this bug for months, but made a ton of other fixes. Now I can't repro anymore. Here's hoping it's accidentally fixed! :)

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on the client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb --dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS> -d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let you know if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

Crazy, I can't repro! Which OS? I'll make a VM. I want this solved before I
release an official version!
On 20 Jan 2015 12:14, "Scoubi"<EMAIL_ADDRESS>wrote:

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on the client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb --dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS> -d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let you know
if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70724397.

Client
mats@insomniac:~/dns2tcp-0.5.2/client$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:        14.04
Codename:       trusty
Server
mats@Vinos-223:~$ nc --version
nc: invalid option -- '-'
nc -h for help
mats@Vinos-223:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux Kali Linux 1.0.9
Release:        Kali Linux 1.0.9
Codename:       n/a

Web Site : www.travelhard.com
On Tue, Jan 20, 2015 at 5:55 PM, Ron<EMAIL_ADDRESS>wrote:

Crazy, I can't repro! Which OS? I'll make a VM. I want this solved before
I
release an official version!
On 20 Jan 2015 12:14, "Scoubi"<EMAIL_ADDRESS>wrote:

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on the
client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb --dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS> -d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let you know
if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70724397.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70751827.

Cool, I'll grab that version of Ubuntu and give it a shot!
Any specific configuration/installation options that might affect things?
Any updates after installing?
FWIW, I'm in the process of moving and most of my gear is packed up. I
don't expect to get to this for a week or two. :)
On Wed, Jan 21, 2015 at 10:17 AM, Scoubi<EMAIL_ADDRESS>wrote:

Client
mats@insomniac:~/dns2tcp-0.5.2/client$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Server
mats@Vinos-223:~$ nc --version
nc: invalid option -- '-'
nc -h for help
mats@Vinos-223:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux Kali Linux 1.0.9
Release: Kali Linux 1.0.9
Codename: n/a

Web Site : www.travelhard.com
On Tue, Jan 20, 2015 at 5:55 PM, Ron<EMAIL_ADDRESS>wrote:

Crazy, I can't repro! Which OS? I'll make a VM. I want this solved
before
I
release an official version!
On 20 Jan 2015 12:14, "Scoubi"<EMAIL_ADDRESS>wrote:

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on the
client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb --dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS> -d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let you
know
if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70724397.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70751827.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70890928.

You know, if you want I can share my screen.
The problem might be with the configuration of my domain (or lack of)
I beleive both system are fully updated (I'm root on the server not on the
client)

Web Site : www.travelhard.com
On Wed, Jan 21, 2015 at 1:25 PM, Ron<EMAIL_ADDRESS>wrote:

Cool, I'll grab that version of Ubuntu and give it a shot!
Any specific configuration/installation options that might affect things?
Any updates after installing?
FWIW, I'm in the process of moving and most of my gear is packed up. I
don't expect to get to this for a week or two. :)
On Wed, Jan 21, 2015 at 10:17 AM, Scoubi<EMAIL_ADDRESS>wrote:

Client
mats@insomniac:~/dns2tcp-0.5.2/client$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Server
mats@Vinos-223:~$ nc --version
nc: invalid option -- '-'
nc -h for help
mats@Vinos-223:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux Kali Linux 1.0.9
Release: Kali Linux 1.0.9
Codename: n/a

Web Site : www.travelhard.com
On Tue, Jan 20, 2015 at 5:55 PM, Ron<EMAIL_ADDRESS>wrote:

Crazy, I can't repro! Which OS? I'll make a VM. I want this solved
before
I
release an official version!
On 20 Jan 2015 12:14, "Scoubi"<EMAIL_ADDRESS>wrote:

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on the
client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb --dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS> -d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let you
know
if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron<EMAIL_ADDRESS>wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70724397.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70751827.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70890928.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70892358.

Whether your domain is configured right or wrong, it shouldn't cause the
client to segfault. That's a problem with the client, for sure.
Can you stand up the dnscat server right now, and give me the info to
connect to it? I'll do a quick test to see if I can get the client to crash
on my end. If I can, then we're golden!
On Wed, Jan 21, 2015 at 10:31 AM, Scoubi<EMAIL_ADDRESS>wrote:

You know, if you want I can share my screen.
The problem might be with the configuration of my domain (or lack of)
I beleive both system are fully updated (I'm root on the server not on the
client)

Web Site : www.travelhard.com
On Wed, Jan 21, 2015 at 1:25 PM, Ron<EMAIL_ADDRESS>wrote:

Cool, I'll grab that version of Ubuntu and give it a shot!
Any specific configuration/installation options that might affect
things?
Any updates after installing?
FWIW, I'm in the process of moving and most of my gear is packed up. I
don't expect to get to this for a week or two. :)
On Wed, Jan 21, 2015 at 10:17 AM, Scoubi<EMAIL_ADDRESS>wrote:

Client
mats@insomniac:~/dns2tcp-0.5.2/client$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Server
mats@Vinos-223:~$ nc --version
nc: invalid option -- '-'
nc -h for help
mats@Vinos-223:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux Kali Linux 1.0.9
Release: Kali Linux 1.0.9
Codename: n/a

Web Site : www.travelhard.com
On Tue, Jan 20, 2015 at 5:55 PM, Ron<EMAIL_ADDRESS>wrote:

Crazy, I can't repro! Which OS? I'll make a VM. I want this solved
before
I
release an official version!
On 20 Jan 2015 12:14, "Scoubi"<EMAIL_ADDRESS>wrote:

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on the
client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb --dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS> -d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let
you
know
if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron<EMAIL_ADDRESS>

wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70724397.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70751827.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70890928.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70892358.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70893527.

Here's the coredump

Web Site : www.travelhard.com
On Wed, Jan 21, 2015 at 1:38 PM, Ron<EMAIL_ADDRESS>wrote:

Whether your domain is configured right or wrong, it shouldn't cause the
client to segfault. That's a problem with the client, for sure.
Can you stand up the dnscat server right now, and give me the info to
connect to it? I'll do a quick test to see if I can get the client to
crash
on my end. If I can, then we're golden!
On Wed, Jan 21, 2015 at 10:31 AM, Scoubi<EMAIL_ADDRESS>wrote:

You know, if you want I can share my screen.
The problem might be with the configuration of my domain (or lack of)
I beleive both system are fully updated (I'm root on the server not on
the
client)

Web Site : www.travelhard.com
On Wed, Jan 21, 2015 at 1:25 PM, Ron<EMAIL_ADDRESS>wrote:

Cool, I'll grab that version of Ubuntu and give it a shot!
Any specific configuration/installation options that might affect
things?
Any updates after installing?
FWIW, I'm in the process of moving and most of my gear is packed up. I
don't expect to get to this for a week or two. :)
On Wed, Jan 21, 2015 at 10:17 AM, Scoubi<EMAIL_ADDRESS>wrote:

Client
mats@insomniac:~/dns2tcp-0.5.2/client$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Server
mats@Vinos-223:~$ nc --version
nc: invalid option -- '-'
nc -h for help
mats@Vinos-223:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux Kali Linux 1.0.9
Release: Kali Linux 1.0.9
Codename: n/a

Web Site : www.travelhard.com
On Tue, Jan 20, 2015 at 5:55 PM, Ron<EMAIL_ADDRESS>wrote:

Crazy, I can't repro! Which OS? I'll make a VM. I want this solved
before
I
release an official version!
On 20 Jan 2015 12:14, "Scoubi"<EMAIL_ADDRESS>wrote:

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on
the
client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb --dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS>
-d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let
you
know
if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron <
<EMAIL_ADDRESS>

wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

—
Reply to this email directly or view it on GitHub
<
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70724397>.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70751827.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70890928.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70892358.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70893527.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70894884.

Hey!
Me again. this time with a good news. I just save you some reverse
engeneering / linux install and other headaches.
After recompiling dnscat on the saver it seems the problem is now fixed.
Look at this beatifull output : mats@insomniac:~/dnscat2/client$ ./dnscat
t.hehe.ca
[[ WARNING ]] :: INPUT: Command
[[ WARNING ]] :: Session successfully created: 19730
[[ WARNING ]] :: Session creation request
[[ WARNING ]] :: Setting config: max_packet_length => 112
[[ WARNING ]] :: OUTPUT: DNS tunnel to t.hehe.ca via <IP_ADDRESS>:53
Got a command: COMMAND_EXEC [request] :: request_id: 0x0001 :: name:
executing ls :: command: ls
[[ WARNING ]] :: Session successfully created: 3025
[[ WARNING ]] :: Session creation request
[[ WARNING ]] :: Started: ls (pid: 763)
Response: COMMAND_EXEC [response] :: request_id: 0x0001 :: session_id:
0x0bd1
[[ WARNING ]] :: Session closure request: 3025
[[ WARNING ]] :: Session 3025 is out of data and closed, killing it!
[[ WARNING ]] :: Trying to close a closed session: 3025
[[ WARNING ]] :: Session closure request: 3025
[[ ERROR ]] :: Tried to access a non-existent session (handle_packet_in):
3025
[[ ERROR ]] :: Tried to access a non-existent session (handle_packet_in):
3025
Got a command: COMMAND_PING [request] :: request_id: 0x0002 :: data:
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Got a ping request! Responding!
Response: COMMAND_PING [response] :: request_id: 0x0002 :: data:
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
I guess I pulled the new code but forgot to recompile / make clean
Anyway, seems you are ready for a release! :)
Hope your new home is nice and that the moving went well!
Yes, it's 6:40 am here and I'm awake since 5am. Thanks to ybaby girl...
Take care,
Mat.

Web Site : www.travelhard.com
On Wed, Jan 21, 2015 at 1:57 PM, Mathieu<EMAIL_ADDRESS>wrote:

Here's the coredump

Web Site : www.travelhard.com
On Wed, Jan 21, 2015 at 1:38 PM, Ron<EMAIL_ADDRESS>wrote:

Whether your domain is configured right or wrong, it shouldn't cause the
client to segfault. That's a problem with the client, for sure.
Can you stand up the dnscat server right now, and give me the info to
connect to it? I'll do a quick test to see if I can get the client to
crash
on my end. If I can, then we're golden!
On Wed, Jan 21, 2015 at 10:31 AM, Scoubi<EMAIL_ADDRESS>wrote:

You know, if you want I can share my screen.
The problem might be with the configuration of my domain (or lack of)
I beleive both system are fully updated (I'm root on the server not on
the
client)

Web Site : www.travelhard.com
On Wed, Jan 21, 2015 at 1:25 PM, Ron<EMAIL_ADDRESS>wrote:

Cool, I'll grab that version of Ubuntu and give it a shot!
Any specific configuration/installation options that might affect
things?
Any updates after installing?
FWIW, I'm in the process of moving and most of my gear is packed up.
I
don't expect to get to this for a week or two. :)
On Wed, Jan 21, 2015 at 10:17 AM, Scoubi<EMAIL_ADDRESS>wrote:

Client
mats@insomniac:~/dns2tcp-0.5.2/client$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Server
mats@Vinos-223:~$ nc --version
nc: invalid option -- '-'
nc -h for help
mats@Vinos-223:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux Kali Linux 1.0.9
Release: Kali Linux 1.0.9
Codename: n/a

Web Site : www.travelhard.com
On Tue, Jan 20, 2015 at 5:55 PM, Ron<EMAIL_ADDRESS>wrote:

Crazy, I can't repro! Which OS? I'll make a VM. I want this
solved
before
I
release an official version!
On 20 Jan 2015 12:14, "Scoubi"<EMAIL_ADDRESS>wrote:

Hi,
I just reinstall dnscat2 on a new server. Pull the new code on
the
client
and compile
-rwxr-xr-x 1 mats users 243821 Jan 20 14:41 dnscat
I'm using IP not DNS and it still crash.
mats@Vinos-223:~/dnscat2/server$ sudo ruby dnscat2.rb
--dnshost
<IP_ADDRESS> -e info
mats@insomniac:~/dnscat2/client$ ./dnscat --host <IP_ADDRESS>
-d
I've attached the two screen capture.
I'll wait until my domain is pointed to the new IP and will let
you
know
if
it works.
Hope it helps...
Mat.

Web Site : www.travelhard.com
On Tue, Jan 13, 2015 at 10:12 AM, Mathieu<EMAIL_ADDRESS>wrote:

I'll look into it next week, thanks dude :)

Web Site : www.travelhard.com
On Mon, Jan 12, 2015 at 12:36 PM, Ron <
<EMAIL_ADDRESS>

wrote:

Closed #4 https://github.com/iagox86/dnscat2/issues/4.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#event-217531905.

—
Reply to this email directly or view it on GitHub
<
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70724397>.

—
Reply to this email directly or view it on GitHub
<
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70751827>.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70890928.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70892358.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70893527.

—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/4#issuecomment-70894884.