[bug] when I send message, return error 11 try again , and then i found sctp_lower_sosend internal run error

It is a but that total_output_queue_size is 0 and chunks_on_outqueue is 1. Do you have a way to reproduce this issue?

I write a screen share app , one app collect screen data  and send data to another app.The app  it collect screen data 40 times  per second , and one times  collect 1024 byte .  It send data through usrsctp send api  to  another app。 Usually one time test takes 15 minutes .Almost ,It send 40 * 1024 * 15bytes (40 times * 1024byte * 15 min)data per test.   I have been testing the screen sharing function  for two days, may be 40  times , and this error will recur once。

Ordered or unordered? How many and which streams? Reliable or unreliable?

below  is my param , i have almost 1006 streams
struct sctp_sendv_spa spa;
(void) memset_s(&spa, sizeof(struct sctp_sendv_spa), 0, sizeof(struct sctp_sendv_spa));
spa.sendv_sndinfo.snd_sid = 1005;
spa.sendv_sndinfo.snd_flags = SCTP_EOR;
spa.sendv_prinfo.pr_policy = SCTP_PR_SCTP_RTX;
spa.sendv_prinfo.pr_value = 0;
spa.sendv_flags |= SCTP_SEND_PRINFO_VALID;

Can I circumvent this problem like this

Can't say if you are fixing an incorrect chunks_on_out_queue or if you are setting chunks_on_out_queue to the wrong value. Depending on that it might result in unexpected behaviour in other places.
I guess the best is to fix the bug which results in the inconsistent variables...

Will all the memory related to these two variables be recycled when I call the sctp close method?   and will you find this bug and fix it in the near future.

and i also fix it in this method . but i do not know , does it is right

Will all the memory related to these two variables be recycled when I call the sctp close method? and will you find this bug and fix it in the near future.

The memory should be freed when the association is freed.
When the bug is fixed depends on how easy it is to reproduce the issue and how much time I have. Please note that this project is completely voluntary and done in my spare time.

and i also fix it in this method . but i do not know , does it is right

Without knowing the bug, it is hard to say if this would improve things or not...


[FEATURE] Name new playlist popup

User Story
For example:
As a developer I want to add a popup which lets the user name the playlist they're creating.
Priority

[ ] High
[ ] Medium
[x] Low

Describe the solution you want to implement
Simple react popup with input box and create/cancel buttons, that passes the entered text through to current endpoint.

Closed as a duplicate of #36 =)


Install fails for conda

Running conda install -c bjodah chempy pytest., I get the following error:
(base) CHEM-67816:~ n00002621$ conda install -c bjodah chempy pytest
Collecting package metadata: done
Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

  - chempy -> pulp[version='>=1.6.8']
  - chempy -> pyodesys[version='>=0.12.4'] -> pycvodes[version='>=0.11.9']
  - chempy -> pyodesys[version='>=0.12.4'] -> pygslodeiv2[version='>=0.9.1']
  - chempy -> pyodesys[version='>=0.12.4'] -> pyodeint[version='>=0.10.1']
  - chempy -> pyodesys[version='>=0.12.4'] -> pysym
  - chempy -> pyodesys[version='>=0.12.4'] -> python-symengine
  - chempy -> pyodesys[version='>=0.12.4'] -> symcxx
  - chempy -> quantities[version='>=0.12.1']

Thank you for the report. I have suspected this, unfortunately conda-forge is moving faster than what I'm able to keep up with. At some point I hope to be able to put chempy on conda-forge, in the meantime, using pip under conda should still allow you to install chempy.


Expose HTTP client for custom AEM tasks

Imagine connecting some endpoints logic within one task
task transferDataToAem {
    doLast {
         def values = aem.rest { it.json { it.get('https://baconipsum.com/api/?type=meat-and-filler') } }
         aem.sync { it.post('/bin/my-service/posts', ['values': values] }
    }
}

snippet above will call any endpoint by exposed http client like http://unirest.io/ , then response will deserialized from json to object, then that object serialized again when passed as request post data to AEM instance endpoints.
todo: also introduce aem.sync('*-author') signature for nice filtering / also useful in scripting

also introduce dynamic instance definition e.g
def instance = aem.instance('http://a:4502')
instance.sync() // ...

both general purpose http client and AEM http client should have methods like download (file)

imagine
aem.sync {
   await()
   deployPackage(project.file('myPackage.zip'))
}

implemented as aem.actions.await()
also calls to external endpoints supported via
tasks {
    register("deployReleasedContent") {
        val downloadedFile = aem.http {
            basicUser = 'xxx'
            basicPassword = 'yyy'

            downloadTo("http://artifactory.com/xxx/yy/backup.zip", project.projectDir)
        }

        aem.sync { deployPackage(downloadedFile) } // on all instances
        // aem.instance("local-publish").sync { deployPackage(downloadedFile) } // on named instance
        // aem.instance("http:///<IP_ADDRESS>").sync { deployPackage(downloadedFile) } // on ad hoc defined instance
    }

}

implemented, to be released within 6.x soon


segfault when releasing a thread

I see apparently at random, a segmentation violation.
Bcktrace is
(gdb) bt
#0  raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  <signal handler called>
#2  __new_sem_post (sem=0x21) at sem_post.c:36
#3  0x00007f38785080f9 in PyThread_release_lock ()
   from /lib/x86_64-linux-gnu/libpython3.9.so.1.0
#4  0x00007f3878570be9 in ?? () from /lib/x86_64-linux-gnu/libpython3.9.so.1.0
#5  0x00007f38788d4a2a in release_interpreter (idata=0x55da959531c0)
    at mod_python.c:306
#6  python_handler (req=0x7f387450d0a0, phase=<optimized out>)
    at mod_python.c:1573
#7  0x000055da949c4bb0 in ap_run_handler ()
#8  0x000055da949c51a6 in ap_invoke_handler ()
#9  0x000055da949ddabb in ap_process_async_request ()
#10 0x000055da949ddcfe in ap_process_request ()
#11 0x000055da949d9bad in ?? ()
#12 0x000055da949ce860 in ap_run_process_connection ()
#13 0x00007f3878960133 in ?? () from /usr/lib/apache2/modules/mod_mpm_worker.so
#14 0x00007f3878c5eea7 in start_thread (arg=<optimized out>)
    at pthread_create.c:477
#15 0x00007f3878b8edef in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Looks like we're trying to release a semaphore we don't hold.
Python 3.9.1 (Debian build), Apache2.4.46-4 (Debian); mod_python from  88e444429ec with the libpython fix.
Using mpm_worker if that makes a difference.

More debugging --- loaded libpython-3.9d.so with debugging syms;  the bug is because we're trying to release the curent thread.

I'm not set up to test/verify any of this so if you get to the bottom of it it'd be fantastic. It's (at first glance) code that stood the test of time, so I wonder if there is something about Python 3.9.1 - perhaps it's doing something differently?

Also been getting this for several months, basically since python went to 3.9 it has been happening.  Using version 3.8 seems to make it go away, not really best practices to do that though.

Commenting out the call to PyThreadState_Clear(tstate); near line 306 of mod_python.c makes the issue go away.
There is only one documented change for this function: from Python 3.9 on it calls the PyThreadState.on_delete callback.

We use httpd docker images which recently switched from debian buster to bullseye. I now also see the Segmentation fault errors with my PythonAuthenHandler.
It looks like the errors happen mainly right after a restart of httpd.
Is there anything I can do to prevent these errors?

This opens a python file I've been running since python 3.9 at least 2 years ago.  The file is called several times per second 24/7.  I'm now running python 3.11 and is segfaults horribly.  Commenting out PyThreadState_Clear(tstate); fixed it.
Just a confirmation that wom-bat patch works.

So should that line be wrapped in something like so
#if PY_MAJOR_VERSION == 3  && PY_MINOR_VERSION > 9
    PyThreadState_Clear(tstate);
#endif

So should that line be wrapped in something like so
#if PY_MAJOR_VERSION == 3  && PY_MINOR_VERSION < 10
    PyThreadState_Clear(tstate);
#endif

Totally makes sense.  Thanks!

Could you confirm that this works for you? I'm currently not set up to test it. If it works, then a pull-request would be much appreciated, if not let me know and I'll add it in myself. Thank you!

That's okay, I took care of it, thanks for your help!

This was fixed as >= 3.10, but reported against 3.9 too. Is that related, or is #122 a different bug

@stefanor I don't have the set up to test it - if you can confirm that the fix should include 3.9 too that'd be much appreciated.

I'm afraid it's present in 3.9 too.  I didn't realised it immediately.  Only when I installed debian 12 and after many useless edits in my python files because I had a lot of trouble and noticed this fix applied to 3.11 has nothing to do with my python files being bad because the bug was suddenly gone.  It was related to this bug.  Sorry I forgot to report it.  I remember clearly I had to switch to old apache module whenever I wanted to run some python 3 code.
In other words, it was fine on debian 10, broken in debian 11 (with 3.9) and fine again in debian 12, thanks to this fix.

@i300220 so the fix should really be

#if PY_MAJOR_VERSION == 3  && PY_MINOR_VERSION < 9
   PyThreadState_Clear(tstate);
#endif

do this look reasonable?

@grisha that's right.  thanks!


[FEATURE] Detailed exception data for InternalServerError

Is your feature request related to a problem?
I am using the client to communicate with an OpenSearch instance that uses the ML Commons plugin.
With the ML commons plugin, the model must be loaded each time the OpenSearch server restarts. The model can only be loaded via an API request.
If I make a query using a model id for a model that is not loaded, the client throws the following exception:
OpenSearch::Transport::Transport::Errors::InternalServerError

With the message:
[500] {"error":{"root_cause":[{"type":"m_l_exception","reason":"model not loaded"}],"type":"m_l_exception","reason":"model not loaded"},"status":500}

What solution would you like?
While the information in the exception message does contain the relevant information, it's clunky because I need to trim the [500] in order to parse the JSON in the message.
Would would be ideal, is if the exception had a status attribute and parsed_data which contained the response as a hash containing the parsed data.
An example of usage would be:
def my_search_method(index, body)
  client.search(index: index, body: body)
rescue OpenSearch::Transport::Transport::Errors::InternalServerError => e
  if e.status == 500 && e.parsed_data["error"]["root_cause"][0]["reason"] == 'model not loaded'
    load_model
  end
end

What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
The alternative is to trim the [500]  from the beginning and the parse the rest. This would work but it's prone to errors and also a bit clunky.
Do you have any additional context?
Hopefully I've provided enough context above but happy to clarify and questions.

That makes sense @dblock. Just to clarify though, are you suggesting that in terms of design, or should that currently work?


Trouble with package build - specreader errors

After checking out 2.0-stable on main branch after building toolchain using: make toolchain REBUILD_TOOLS=Y, I tried to build a single package using: make build_packages -j$(nproc) QUICK_REBUILD_TOOLCHAIN=Y SRPM_PACK_LIST="kernel-hci"  Got specreader error.  Working on my fork, just rebased upstream main.  Not sure how to resolve.

Also tried to just build iso from prebuilt pac

kages per documentation and it fails also with imageconfigvalidator error

git log:

Hi @cwyborny

Working on my fork, just rebased upstream main. Not sure how to resolve.

Are there any changes in your fork ? Can you please provide some more repro steps, if possible.
I tried to repro the issue but could not: (specreader & the build proceeds fine for 2.0-stable)
mfrw in 🌐 curie in ~/ma/CBL-Mariner (main) [$?]
fsh ❯ git checkout 2.0-stable
HEAD is now at 78094693e CodeQL Mariner toolkit (#6885) (#6902)
mfrw in 🌐 curie in ~/ma/CBL-Mariner/toolkit (7809469) [$?]
fsh ❯ git log --oneline -1
78094693e (HEAD, tag: 2.0.20231205-2.0, tag: 2.0-stable) CodeQL Mariner toolkit (#6885) (#6902)
mfrw in 🌐 curie in ~/ma/CBL-Mariner/toolkit (7809469) [$?]
fsh ❯ sudo make build-packages QUICK_REBUILD_TOOLCHAIN=Y SRPM_PACK_LIST="kernel-hci"
Downloading toolchain RPM: filesystem-1.1-17.cm2.x86_64.rpm
Downloading toolchain RPM: kernel-headers-<IP_ADDRESS>-4.cm2.noarch.rpm
Downloading toolchain RPM: glibc-2.35-6.cm2.x86_64.rpm
Downloading toolchain RPM: glibc-devel-2.35-6.cm2.x86_64.rpm
.... snip ....

INFO[0000][scheduler] Reading DOT graph from /home/mfrw/mariner-org/CBL-Mariner/build/pkg_artifacts/preprocessed_graph.dot
INFO[0000][scheduler] Reading DOT graph from /home/mfrw/mariner-org/CBL-Mariner/build/pkg_artifacts/preprocessed_graph.dot
INFO[0000][scheduler] Successfully created solvable subgraph
INFO[0000][scheduler] Building 69 nodes with 12 workers
INFO[0000][scheduler] Building: kernel-hci-<IP_ADDRESS>-1.cm2.src.rpm
.... snip ....

I wouldn't expect any changes in the fork for 2.0-stable as the changes I'm working on were prior to this tag, but with moving tags, I might not be fully aligned on my local system.  The package I was trying test build, builds on another system, so that leads me to believe I have something wrong on this local version.  This issue can be closed for now.


Increase timeouts in the "must check that pasting html just keep the text" integration test

This is temporary fix to reduce the number of intermittent failures for this test until we have the permanent fix tracked in #17931.
In draft because I'd like to run this isolated test a couple of times on the Windows bot first. It's not ideal, but it should buy us time to think of a proper fix while avoiding being distracted too often by this test failing intermittently (it just happened again in http://<IP_ADDRESS>:8877/32892d2cf177f38/output.txt).

/botio-windows integrationtest

/botio-windows integrationtest

/botio-windows integrationtest

/botio-windows integrationtest

/botio integrationtest

Note that the Linux failure above is unrelated to the changed timeouts and also happened before already (but fortunately occurs much less often than the issue on the Windows bot that this PR aims to avoid).

Yikes, it looks like increasing the timeouts doesn't do as much as I had hoped. Oh well, it was worth a try, but I guess we'll have to keep it like this and work on the proper fix in the meantime instead :-/


Change Action.route to Action.with

So you call route helpers like this link "edit", to: MyAction::Edit.with(id: something.id)
Another alternative is MyAction::Edit(id: something.id) which is sort, but maybe a bit magical? I'm not sure about it, but it is nice that it's so short. EDIT: This won't work: https://github.com/luckyframework/web/issues/170#issuecomment-340450926
See discussion in Gitter https://gitter.im/luckyframework/Lobby?at=59f7126fd6c36fca31b4223c
From @edwardloveall

I was thinking about routing last night, and it feels a little weird to me that it's link "foo", to: SomeClass OR link "foo", to: SomeClass.route(with_params)
from an API, it's seems inconsistent that I'm linking to either a class, or a or whatever route returns
i see how it works on link internally, but I wonder if it would make more sense for the params version to look like link "foo", to: SomeAction, params: with_params
.route was a bit of a head scratcher when I first saw it
probably because it's not clear to me that the route method would take params (as opposed to a route, or location)
actually, changing route to with_params or params would also solve this

My response:

I was thinking it was confusing too but couldn’t come up with a good name. I think your suggestion to rename is great. I think params might be confusing because it seems like it would return a params object or something. with_params is super clear but a bit long. Maybe with would be a good middle ground? link to: Topics::Show.with(topic) not quite as clear as with_params, but at least it’s not actively confusing people, and this way it’s not so much to type once you do learn it. Thoughts?

Another thought was: link "edit", to: MyAction::Edit(id: something.id)
This is a little strange because it looks like Edit is a method. Also, I don't know enough crystal to know if that will even work.

Just tried it out and it's a syntax error. Doesn't look like that's possible :(

That's probably for the best.

what about an overloaded link helper?
link "list", to: MyAction::Index
link "edit", to: MyAction::Edit, id: something.id

Sadly that won't work because it's not clear if that should be an HTML id attribute or an id for the link. I think it also makes it less clear what's happening. So if you wanted to build your own helper method it would be hard to tell what to do. By keeping it as a class method it makes it clear how you could call it from your own methods if you wanted to. Like in emails or something

I think with is probably pretty good then. New users will have to look it up to understand what it means, but once you learn it, it's probably pretty easy to remember and use correctly.

I agree. It might not make immediate sense, but it's something easy to learn and once you learn it you'll use it all the time and it hopefully won't be an issue :D

I feel for could be a good alternative: Topics::Show.for(topic) / MyAction::Edit.for(id: something.id). Otherwise I think with_params would be better than just with, since slightly less typing is less important than semantic clarity, though one could provide aliases.

I thought about for also. It doesn't feel as good as with to me because for implies the route is about whatever params you're passing into it, which isn't always the case: Topic::Show.for(id: topic.id, articles_since: timestamp, random_seed: seed). Where are with implies data that is coming along with whatever route, which is actually what's happening.
I actually do still like with_params. It's extremely clear and I don't think it passes the "too long" threshold.

Better example: Product::Index.for(region: region.id, guest: true, coupon_offer: coupon). It's stops really becoming for that product or products because sometimes there are extra things that need to be in whatever view or action you're visiting.

Yeah, I guess we can agree to disagree on for 😉 I still think of as "the action for a given set of params", which makes sense for your example too in my book.
That said, with_params is unambiguous and we all seem to like it, so 👍 ?

More up to @paulcsmith on that one. He thought it was too long.

Yeah I think if it were used infrequently then with_params would be perfect, but it’s going to be used a ton and is not too tricky to learn. So I think the trade off is that it’s slightly harder to grok at first glance, but then you learn it quickly and have less typing and reading to do from then on.
I’m asking some others for advice on this, but I think this is the direction that will result in best long term happiness. Does that make sense?

On Oct 31, 2017, at 9:22 AM, Edward Loveall<EMAIL_ADDRESS>wrote:
More up to @paulcsmith on that one. He thought it was too long.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

with is crystal clear (sorry, not sorry) to me given the context

We’re Lucky to have you’re insights and puns @derekprior


error: while type checking after reload with money conversion

Opening the following URL shows an error: https://numbat.dev/?q=10+€+to+USD. I presume that is because monetary conversion are not loaded at that point yet...

Thank you for reporting this.
Yes. The way currencies work right now is a bit of a hack: https://github.com/sharkdp/numbat/issues/177#issuecomment-1736087839
I have ideas on how to improve this situation, which would also solve your case. See https://github.com/sharkdp/numbat/issues/107 for details.

This should work now :smile:
Not just on the web, but also on the command line:
▶ numbat -e "10€ to $"

  10 euro ➞ dollar

    = 10.539 $    [Money]


How to add client_secret in an auth code flow?

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.18.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.0.4
Description
We use a third party IDP to make the logins, and this IDP demands a client_secret in the token endpoint. (i don't know why)
I looked at the code and found basic implementation for adding client_secret in the AuthorizationCodeClient but it is not possible to provide the clientCredentials in the MSAL config. When the config is built it takes de DEFAULT_CLIENT_CREDENTIALS and therefore it's always empty.
Is this correct or did I miss something?
MSAL Configuration
No response
Relevant Code Snippets
No response
Identity Provider
Other
Source
External (Customer)

@domiSchenk You are right, there isn't a way to pass in client_secret as msal-browser and msal-angular only support public clients, as they run in an environment (a web browser). If you need to support confidential clients you are welcome to try msal-node.

Does the nodejs version run in the browser or are there nodejs specific api calls?
i solved it with patching the angular/browser modul, so its reads from localstorage. This works for now.
I have to ask this provider why they wand a client secret in this environment.


feat: reenable check for visibility modifiers

Fixes #278

LGTM, please merge.

Should I merge even if there are several hundred places in Angular that will become errors if this check is turned on?

Yes, but that makes you responsible to fix those in Angular when you upgrade ts2dart :-)

I've already fixed all of the private fields without leading underscores. I would actually like to allow public fields with leading underscores since that is helpful for dart2js. What do you think?

Merged as e288c35.
As discussed offline, let's make all those public fields leading with an underscore in angular private, as they should be.


Add support for kubectl port-forward

This change is

Review status: 0 of 13 files reviewed at latest revision, 2 unresolved discussions.

.circleci/config.yml, line 165 at r1 (raw file):

      name: install kubectl
      command: |
        curl -L https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl -o /bin/kubectl

shouldn't we pin to the same version as in glide? Right now we're fetching 1.8 right?

images/Dockerfile.build-base, line 55 at r1 (raw file):

# Install kubectl
RUN curl -L https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl -o /bin/kubectl

same question as above

Comments from Reviewable

Review status: 0 of 13 files reviewed at latest revision, 2 unresolved discussions.

.circleci/config.yml, line 165 at r1 (raw file):
Previously, pigmej (Jędrzej Nowak) wrote…
shouldn't we pin to the same version as in glide? Right now we're fetching 1.8 right?

I'm assuming that the newest kubectl should be working with older clusters.

Comments from Reviewable

Review status: 0 of 13 files reviewed at latest revision, 2 unresolved discussions.

.circleci/config.yml, line 165 at r1 (raw file):
Previously, lukaszo (Łukasz Oleś) wrote…
I'm assuming that the newest kubectl should be working with older clusters.

IMO it would be better to 1) use specific version of kubectl 2) add sha1sum check like this: echo "XXXXXXXXXXXXXXX... /usr/local/bin/kubectl" | sha1sum -c

images/Dockerfile.build-base, line 55 at r1 (raw file):
Previously, pigmej (Jędrzej Nowak) wrote…
same question as above

same as above, IMO need fixed version + kubectl sha1sum check

Comments from Reviewable

Review status: 0 of 13 files reviewed at latest revision, 2 unresolved discussions.

.circleci/config.yml, line 165 at r1 (raw file):
Previously, ivan4th (Ivan Shvedunov) wrote…
IMO it would be better to 1) use specific version of kubectl 2) add sha1sum check like this: echo "XXXXXXXXXXXXXXX... /usr/local/bin/kubectl" | sha1sum -c

Done.

images/Dockerfile.build-base, line 55 at r1 (raw file):
Previously, ivan4th (Ivan Shvedunov) wrote…
same as above, IMO need fixed version + kubectl sha1sum check

Done.

Comments from Reviewable

Reviewed 10 of 13 files at r1, 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

Reviewed 10 of 13 files at r1, 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable


[WebChat] ConversationUpdate Activity Event issue

System Information (Required)

SDK Language:  .NET/C#

SDK Version: Latest
Channels : WebChat & Emulator

Development Environment: LOCALHOST

Issue Description
I have a simple bot created to send a welcome message with menu selection using adaptivecard as activity attachment. I'm using the ConversationUpdate event to send this welcome message. Now, once user click on any  menu item it's always coming as "ConversationUpdate" activity type in the message controller in the API. Issue is with the webchat.  Emulator  working fine and its coming as "Message" activity type.
Expected Behavior
WebChat should send it as a AcivityType.Message Event when user reponds as the same way as it working in emulator

Please share your code.

Here is the code : https://github.com/sowsan/Bot/tree/master/Bot-Demo/Bot-Demo

@sowsan we are looking into this.  Something is wrong and we are trying to pinpoint exactly what it is.

@msft-shahins, can you please have a look?

I had submitted it in bot webchat as well : https://github.com/Microsoft/BotFramework-WebChat/issues/498

@sowsan I have been tinkering around with your code for the past 2 days.  I was able to get the card and the response to show up in both the webchat and the emulator channels.
The code can be found here
I moved your code around but didn't really change much.  Do you have a use case for trying to handle conversationUpdates in a dialog rather than the message controller?  I ask because I moved the code from the dialog to the controller and I am not sure if that's how you needed it or not.  Please give it a try and see how it works for you
side note.  In webchat control.  When I launch the application from visual studio the card does not appear the first time, but when I refresh it does.  If I copy and paste the URL into a browser window (as a customer would) it also works.  that was the only quirky behavior I found.  Let me know how this works out for you Good Luck.

@JasonSowers can you try this on other channels to see if this is a universal or specific to webchat?

@danmarshall Will do

@JasonSowers thank you. Yes, I have the same issue with the ActivityType.Event. My bot has a functionality to send the proactive messages and I'm doing it today with the Azure fucntions to send the messages. In that case I send a adapative card to the user from the dialogue and I'm getting the same issue there too. So, I thought that if we can fix it in the dialogue then it will fix my other issue as well.

tested with bot emulator & web chat. Issue seen only with webchat

@sowsan tested my modified code?  or the original?

Thanks @sowsan . Can you specify how you are using WebChat:

In the Bot Framework Dev Portal
In an Iframe from an Embed code from the Dev Portal
From your own deployment of the code from GitHub

@dandriscoll , both 1&2

@sowsan can you provide your bot id ?

@JasonSowers i was able to fix it by putting the code in the messagecontroller like you did, but in my case I have to execute it via the dialogue. Thanks again !

@sowsan are you still having trouble with this, or have you resolved it?

@JasonSowers  yes, still its an issue. Anyone was able to reproduce the issue and find a resolution ?

Between, I was able to reproduce the issue with DirectLine Channel as well , so its just webchat, I think webchat is also using DirectLine so it might be DirectLine related.

Anyone facing the same issue ? its a real blocker to one of my projects now :(

@sowsan it would be very helpful to me if you can deploy this bot so that I can run WebChat against it.

currently its privately tested , is this enough ? https://dev.botframework.com/bots?id=uChat

@sowsan  - Yes I was able to see it.

@sowsan - please see #2093
You should expect to see at least 2 ConversationUpdates : first for the bot being added to the conversation, second for the user being added. I believe that the initial button click from the user is the signal that they have entered the conversation.
To avoid being triggered by either, compare the from.id with your bot id to see which of the 2 ConversationUpdates is happening.

@sowsan Here is a sample of what @danmarshall is talking about
else if (message.Type == ActivityTypes.ConversationUpdate)
            {
                IConversationUpdateActivity iConversationUpdated = message as IConversationUpdateActivity;
                if (iConversationUpdated != null)
                {

                    foreach (var member in iConversationUpdated.MembersAdded ?? System.Array.Empty<ChannelAccount>())
                    {
                        // if the bot is added, then
                        if (member.Id == iConversationUpdated.Recipient.Id)
                        {
                            //do stuff
                        }
                    }
                }
            }

Thanks, I have already added it in the dialogue code, look like i have to go without dialogue and which is something not a good work around for me.

You can close this issue as I was able to work around it using this model : https://github.com/Microsoft/BotBuilder-Samples/tree/master/CSharp/core-proactiveMessages
Basically I have implemented a different API endpoint to send the proactive reminders instead of another direct client using Azure Function. Because of that I'm not getting any conversationupdated event in the current dialogue and I'm good to stay with the dialogue model. Thanks again for all of your help help and advise. Appreciate it !


@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/pyogrio-feedstock#12.


Regression tests for linear norm model confidence

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

/modeltest
dataset_branch: "new_recommendation"
include:
 - dataset: ["Carbon Bot", "Sara", "Private 1", "Private 3"]
   config: ["all"]


[Bug] Suggestions never appear

👎 Problem
No matter what I do the suggestions never appear, ive tried enabled = true, false, cycling completions manually etc and im definitely logged in with my API key.
Ive also restarted the server and ran the other enable ex commands.
🔢 Steps to reproduce
I'm using mostly the default setup.
👍 Expected behavior
Suggestions should appear
Neovim version (nvim -v)
Stabled 0.10
Operating system (uname -om)
macOS arm64
:checkhealth neocodeium
OK
Relevant log output
No log appears no matter what.

Hello, could you run neovim with NEOCODEIUM_LOG_LEVEL=info nvim  and paste the log here.

Sorry, seems like I can't fix this from plugin side.
Something with this log lines. Not sure why codeium error on this. I know chezmoi cli tool, but why it interacts work codeium in such way?

Wraps: (5) read /Users/SCRUBBED/.local/share/chezmoi
Wraps: (6) is a directory

From my head it could be two issues:

Problem with codeium language server itself, would require some testing from your side. You can try different codeium language server yourself, find it's versions here https://github.com/Exafunction/codeium and just change this line https://github.com/monkoose/neocodeium/blob/4a46f6438bcdb21c562f83036bce75c719834072/lua/neocodeium/binary.lua#L18 to this new version.
Problem with your setup/OS. I can't help there

Glad to hear it.
Which version do you use exactly? For some time I will update it to this version and will consider to add a such option in the future.

Thanks, I have bumped the version.

@Ajaymamtora it totally get skipped from my mind that you can download any specific codeium server binary from https://github.com/Exafunction/codeium/tags, extract it and specify the path to it in neocodeium.setup({ bin = 'path/to/binary' })
So adding new option for specific codeium server number is maybe a little bit more convenient, but at the same time redundant.

I don't think it is a good idea. For example you can try last version 1.16.1 and neocodeium would not work, because they have changed something internally (should investigate what exactly). And the worst codeium doesn't have any documentation, api reference etc.


Adopt XMPP standard set in XEP-0174

For over a decade, XMPP clients can communicate over LAN and "mesh" by publishing their presence using Avahi (also referred to as "Zeroconf"); see XEP-0174: Serverless Messaging.

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. This enables you to plug your laptop or computer into a network and instantly be able to view other people who you can chat with, find printers to print to or find files being shared.

Clients with XEP-0174 support: Gajim * and Kopete, and more...
This would also allow LocalSend to interoperate with Croc, provided Croc would also support XEP-0174.
* Support to Gajim will be restored very soon

I think LocalSend is perfect for distros like postmarketOS which is based on AlpineLinux; yet, my request for LocalSend was rejected due to the lack of Flutter.
As not all distros hvae all packages, but do have Jabber/XMPP clients available, it would be nice to either support XEP-0174 as an extension or, better yet, adopting XEP-0174 as core communication standard for LocalSend.

Hi, implementing XMPP protocol may be considered in the future when directory share (#121), web share (#198) and UI redesign (#300) has been implemented.

im just wondering,  yes jabber has support for p2p signaling over public networking to allow for  key negotiation and eventualy  some form of data connection (that you can either use to send files or (like jingle does) audio / video  conferencing.
so instead of this,   regardless of flutter or just about any language...  why (if localsend can be THE next thing,  it could be) not just re-implement it in a diferent language like c, java, lua or what not.
i absolutely agree that a service such als localsend, that is multi-OS compatible  would absolutely be amazing.  aspecially if for example iphone's get it as a running background service (eventually).  not the less, for those people who build custom OS's for (for example mobile devices, ereaders, media-devices etc... they just just find a way to  build a localsend api version to incorporate into thair devices.

Hi, implementing XMPP protocol may be considered in the future when directory share (#121), web share (#198) and UI redesign (#300) has been implemented.

Can we add this to Roadmap #345 (with the conoditions you specified)?

Well the roadmap is there for the internal team (which is currently only me). Unfortunately, I don't know how XMPP works and I also don't have much time for that. I've added a "help wanted" tag in case someone else want to take this issue.

Or can croc be directly integrated to localsend?

that would be awesome! I am thinking of a qr code implementation where a user simply scans a code (the croc id) and can send files even if outside of the same wifi network (or on a network with a strict firewall)
I also heard that flutter and go work very well together (croc is written in go). Also found this article that maybe is helpful: https://openprivacy.ca/discreet-log/09-flutter-with-native-go-libraries/

Any progress on it?


Refactor config so that api can be unit tested w/out touching the file system

Looks good. Thanks for the suggestions!


creat email inbox in server 404

as<EMAIL_ADDRESS>depand country the website in google colud or vivo paly control application till one can avilible delet doungrous red color and ficilit multy assur
https://github.com/github/docs/edit/main/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
cantain gstritant :-
Gstrite number cumpany with key rsistant phone
douztant number visa
recopy cash inbox replacement automatic hung step

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for the deploy-to-heroku link in your pull request, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

 @hundums.gitbul

@@ -31,3 +31,4 @@ topics:

"About teams"
"Managing team access to an organization repository"

she it woman ?


Attribute for ipv6

Hi !
I have a limitation with the current attribute. I can automate the creation of DNS record with the default_ipv4_address attribute, but I just noticed that there is no default_ipv6_address attribute available to retrieve the IPv6 address of the virtual machine using the QEMU guest agent.
is there a technical limitation of the provider or is it just not implemented yet?

Related to #974

Fixed by v3.0.1-rc2


improve handling of FILTERs with constant expressions

Scope & Purpose
Don't produce FILTER nodes for filter conditions that are known to be always false. Instead, produce a NoResultsNode.
Don't produce FILTER nodes for filter conditions that are known to be always true.
As a side effect, this may optimize certain queries that will not produce any results.

[x] Bug-Fix for devel-branch (i.e. no need for backports?)
[ ] Bug-Fix for a released version (did you remember to port this to all relevant release branches?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)
[x] The behavior change can be verified via automatic tests

Related Information

[x] There is a GitHub Issue reported by a Community User: https://github.com/arangodb/arangodb/issues/9938

Testing & Verification
This change is already covered by existing tests, such as (please describe tests).
https://jenkins01.arangodb.biz/view/PR/job/arangodb-matrix-pr/6114/

https://jenkins01.arangodb.biz/view/PR/job/arangodb-matrix-pr/6115/

Test failures are unrelated to this PR


Blog post for 1.12 has incorrect sample code

The post for 1.12 under extension authoring: https://code.visualstudio.com/updates/v1_12#_extension-authoring
Has
vscode.window.showProgress({
    location: vscode.ProgressLocation.Window,
    title: 'My long running operation'
}, (progress) => {
    // Progress is shown while this function runs.
    // It can also return a promise which is then awaited
    progress.report({ message: 'Doing this' });
    await step1();

    progress.report({ message: 'Doing that' });
    await step2();
})

but the API is withProgress
vscode.window.withProgress({
    location: vscode.ProgressLocation.Window,
    title: 'My long running operation'
}, (progress) => {
    // Progress is shown while this function runs.
    // It can also return a promise which is then awaited
    progress.report({ message: 'Doing this' });
    await step1();

    progress.report({ message: 'Doing that' });
    await step2();
})

ops, nice find

Fix with https://github.com/Microsoft/vscode-docs/commit/e6373790bb7db4c9b35e61ca44df67b1f6c9c6f9


runelite GUI ghosting error

This error occurs intermittently after starting runelite.
When sliding the mousepointer over the GUI tabs on the right side, the pictures disappear and/or duplicates "ghosting".
I will attach some screenshots of the error to see if anyone has the same issue.
I am running Windows 10 Pro 64-Bit

RuneLite version: 1.6.16
Launcher version: 2.1.3

https://github.com/runelite/runelite/wiki/Disable-Hardware-Acceleration

runelite/runelite/wiki/Disable-Hardware-Acceleration

https://github.com/runelite/runelite/wiki/Disable-Hardware-Acceleration

Hi, i tried all the "tricks" in the link for Windows but i keep getting the same issues.
Any more ideas?

join us on discord


$q: Control flow duplication (forking) when uncaught error is handled in .then()

Triggered when:
$q.resolve().then(function() {
  throw new Error();
}).catch(function(e) {
  // ok, but the catch-all handler also receives `e` (incorrect)
});

Correctly handled when:
$q.resolve().then(function() {
  try {
    throw new Error();
  }
  catch(e) {
    return $q.reject(e);
  }
}).catch(function(e) {
  // ok, and the catch-all handler has not been activated (correct)
});

Relevant code: https://github.com/angular/angular.js/blob/c9dffde1cb167660120753181cb6d01dc1d1b3d0/src/ng/q.js#L366

line 365: the Error is correctly passed up the promise chain: deferred.reject(e);
line 366: the Error is also passed to the exceptionHandler(e);, which effectively forks the control flow, if the Promise chain in 1. was not ignored.

Normally this is not a ciritical issue, since exceptionHandler() is usually used to just print errors to the console, however correctly the error would make it to the exceptionHandler() only if it was not ignored by the deferred.reject(e); chain (which, I'm not sure if it's even feasible to implement).
Possibly related; #7992, #13653

This is so by design. Passing it to the $exceptionHandler is not forking the control flow. $exceptionHandler can hardly be used for controlling the flow (in a sensible way) - it's more like a notification hook for the developer imo.
There has been a debate (of medium length) about whether we should pass the thrown error to the $exceptionHandler or not. I think the main problem is that we can't distinguish a deliberately thrown error (e.g. throw new Error('Thrown just to reject the promise')) from an actual programming error (e.g. (undefined).foo).
I think the verdict was that making it configurable won't harm (but we haven't decided on the default setting yet :stuck_out_tongue: )
If anyone wants to submit a PR, that would be awesome (should be an easy change - famous last words).

Thanks for the response!
The control flow is "forked" in a sense that if there is e.g. an "email to developer" in the catch-all handler, and also in the .catch() on the Promise chain, the developer will get two emails:)
I'll see about the PR, I'm super-busy lately.. (aren't we all?)

This sounds like a breaking change, and one goes against the Promise A+ spec - see relevant line here. I would recommend against this.

@wesleycho do you mean "If either onFulfilled or onRejected throws an exception e, promise2 must be rejected with e as the reason." ?
Yes that is the correct behavior and it already happens.
However the problem is that it is not the only thing that happens in that case, but the error is also (and firstly) reported to Angular's uncaught exception handler - which is incorrect because the definition of an uncaught exception is, well, one that is uncaught. However in this particular case the exception is caught by the Promise.then() and then, passed to .catch(), and only if there are no callbacks registered in any of the .catch() upwards in the Promise call chain, only then is the Exception actually uncaught and should be passed to the Angular's $exceptionHandler - IMHO.
https://docs.angularjs.org/api/ng/service/$exceptionHandler

Ah, so you're proposing to just have the exceptionHandler call be removed and let it defer down to the unprocessed exception check then. That sounds reasonable, probably wouldn't be difficult to put together a PR doing so.

@youurayy as stated https://github.com/angular/angular.js/issues/14745#issuecomment-224875715 this was discussed. I cannot speak in behalf of the core team, but I think that the transformation of catching an exception and generating a rejected promise is something that needs to be tracked (and if there is a need for this not to be tracked, then the promise should return a rejected promise).

To be clear, what we are talking here is just this line and that line; whether or not exceptionHandler should be called. We are not debating the rejection; it must happen according to the spec.
What I was proposing above, is to make it configurable - similar to how the user can turn on/off the unhandled rejection error. The user should be able to decide whether the exceptionHandler should be called or not when an error is thrown inside a promise.

@gkalpak - the behavior where the exceptionHandler gets called only when the rejected promise was not handled by any user-space Promise .catch handler -- would that behavior be hard to implement? At the end of the error promise chain, that's where the angular catch-all redirector to exceptionHandler should be sitting I think.

the behavior where the exceptionHandler gets called only when the rejected promise was not handled by any user-space Promise .catch handler -- would that behavior be hard to implement?

Not sure what you mean. Isn't that already implemented?

No, the behavior I'm observing is that the exceptionHandler gets called even when the exception is handled by an user-space .catch handler. Moreover, the exceptionHandler gets to handle the exception before the user-defined .catch handler.

@youurayy, there are several exceptionHandler calls (inside $q). I think the main ones are 2:

Called when an error is thrown (as in throw ...). This is done in addition to rejecting the promise.
Called when there is a possibly unhandled rejection.

The second category is not relevant with what we are discussing here. This issue is about the first category of calls. Regardless of what we do with the first category though, the unhandled rejections will still be treated as they are today (i.e. calling exceptionHandler).

Or maybe I am totally missing your point (it's not that it hasn't hapened before :smiley:).
An example might help:
// Assuming:
function onSuccess1(val) { console.log('onSuccess1'); return val; }
function onSuccess2(val) { console.log('onSuccess2'); return val; }
function onError1(err) { console.log('onError1'); return $q.reject(err); }
function onError2(err) { console.log('onError2'); return $q.reject(err); }
function onError3(err) { console.log('onError3'); }

p1 = somePromise1.then(function () { throw 'Error'; }).then(onSuccess1, onError1);
p2 = somePromise2.then(function () { throw 'Error'; }).then(onSuccess2, onError2).catch(onError3);

For p1, you will see onError1 in the console and the exceptionHandler will be called twice: once for the thrown error and once for the possibly unhandled rejection.
For p2, you will see onError2\nonError3 in the console and the exceptionHandler will be called once: for the thrown error.
I suggest that we make it configurable whether the first call to exceptionHandler is made or not (the one for the thrown error).

We should treat errors thrown in promise callbacks and returned rejections in the same way, all promise libraries do it like that. Let's do it in 1.6.0.


Checked nullable variable still resulting in a null error when used inside an arrow function

Bug Report

I am not sure how to explain this but when I declare a nullable variable and then check it with the non null guard, Typescript still shows me that the variable could be null when used inside an arrow function. When using the same variable outside the arrow function, TS doesn't complain. Neither does it complain if I assign a new variable to the nullable variable and use it inside the arrow function.
🔎 Search Terms

🕗 Version & Regression Information

Playground link with relevant code
💻 Code

export function generateBgsReport(input: number): void {
    let whoa: DObject | null;
    whoa = returnMethod(input)
    if (!whoa) {
        throw new Error();
    }
    const cObjects = [{
        attr1: 'one',
        attr2: 1
    }]
    testMethod(cObjects[0], whoa.dAttr)

    cObjects.map((c) =>
        testMethod(c, whoa.dAttr)
    );

    const check = whoa

    cObjects.map((c) =>
        testMethod(c, check.dAttr)
    );
}

function testMethod(param: CObject, input: string): string {
    return param.attr1 + input
}

type CObject = {
    attr1: string;
    attr2: number;
};

type DObject = {
    dAttr: string;
}

function returnMethod(input: number): DObject | null {
    if (input % 2 === 1) {
        return {
            dAttr: 'test'
        }
    }
    return null
}

🙁 Actual behavior
A checked nullable variable used inside a arrow function is showing that it still could be null
🙂 Expected behavior
After I check a nullable variable outside a arrow function, it should recognize this check even inside an arrow function

See #11498 or its many inbound duplicates

Also see #9998.


code release

Is there any plan to open the code? Looking forward to your reply!

Will be uploading code, models, etc. this week / weekend

Hello, is there still a plan to make the code public?


[Bug]: Update to 3.5

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
Cheat Engine
Expected/Current Behaviour
The app should be up-to-date
Steps to Reproduce
scoop install extras/cheat-engine installs the old version (3.4)

Possible Solution
Update the manifest to reflect the latest changes so it downloads the latest version (3.5)
Scoop and Buckets Version
Current Scoop version:
6a35a22b (HEAD -> develop, origin/develop) fix(scoop-checkup): Change the message level of helpers from ERROR to WARN (#5614)

'main' bucket:
4b149fd65 (HEAD -> master, origin/master, origin/HEAD) zeebe: Update to version 8.2.15

'extras' bucket:
d340aff29 (HEAD -> master, origin/master, origin/HEAD) metasploit-framework: Update to version 6.3.37-20230929103406

'versions' bucket:
e44493250 (HEAD -> master, origin/master, origin/HEAD) webstorm-eap: Update to version 2023.3-233.8264.9

'sysinternals' bucket:
db7ddd5 (HEAD -> main, origin/main, origin/HEAD) zoomit: Update to version 7.1

'php' bucket:
f946dc5 (HEAD -> master, origin/master, origin/HEAD) php8.2: Update to version 8.2.11

'nerd-fonts' bucket:
978fb32 (HEAD -> master, origin/master, origin/HEAD) GlowSansSC-Extended: Update to version 0.93

'nonportable' bucket:
5798404 (HEAD -> master, origin/master, origin/HEAD) burp-suite-pro-np: Update to version 2<IP_ADDRESS>

'java' bucket:
e948d3ee (HEAD -> master, origin/master, origin/HEAD) temurin17-nightly-jre: Update to version 17.0.9-7.0.202309290057

'games' bucket:
af873ddf (HEAD -> master, origin/master, origin/HEAD) ryujinx: Update to version 1.1.1037

'1nfdev_bucket' bucket:
07b79d7 (HEAD -> master, origin/master, origin/HEAD) keys: removed from bucket; switch to use official bucket

'2moveit_scoop-bucket' bucket:
54e4bcb (HEAD -> master, origin/master, origin/HEAD) Create vscode.json

'404NetworkError_scoop-bucket' bucket:
44f8447 (HEAD -> main, origin/main, origin/HEAD) Add powershell 7.3.7 and powershell-preview 7.4.0-preview.6

'42wim_scoop-bucket' bucket:
e0d66ef (HEAD -> master, origin/master, origin/HEAD) msedge-canary: Update to version 119.0.2129.0

'4x0v7_kube-scoop' bucket:
45e5a3c (HEAD -> main, origin/main, origin/HEAD) awsv1: Update to version 1.29.57

'4x0v7_scoop-bucket-codefresh-cli-v2' bucket:
93b751d (HEAD -> main, tag: v0.1.40, origin/main, origin/HEAD) cf: Update to version 0.1.40

'82p_scoop-yubico-bucket' bucket:
13558bc (HEAD -> master, origin/master, origin/HEAD) fix regex yubihsm2-sdk.json

'a4albers_scoop-bucket' bucket:
1288b22 (HEAD -> main, origin/main, origin/HEAD) Update backup.json

'abgox_ownBucket' bucket:
a572ebe (HEAD -> main) add keyviz(按键回显)

'abhimanyu003_scoop-bucket' bucket:
89f481a (HEAD -> main, origin/main, origin/HEAD) Scoop update for sttr version v0.2.18

'acdzh_zpt' bucket:
ba6b487 (HEAD -> master, origin/master, origin/HEAD) trafficmonitor: Update to version 1.84

'ackerr_scoop-bucket' bucket:
302ee12 (HEAD -> master, origin/master, origin/HEAD) Scoop update for lab version v0.4.3

'ACooper81_scoop-apps' bucket:
322cc16cc (HEAD -> master, origin/master, origin/HEAD) MicrosoftEdgeCanary-Portable: Update to version 119.0.2126.0

'ACooper81_scoop-settings' bucket:
bec09a8 (HEAD -> master, origin/master, origin/HEAD) Merge branch 'master' of https://github.com/ACooper81/scoop-settings

'actioninja_scoop-bucket' bucket:
37ddc2c (HEAD -> main, origin/main, origin/HEAD) comtrya: add hash

'adamrodger_scoop-bucket' bucket:
f3a23ef (HEAD -> master, origin/master, origin/HEAD) gctx: upgrade to 0.7.0

'AdmnJ_Custom-Bucket' bucket:
905f7d8 (HEAD -> master, origin/master, origin/HEAD) spotifytesting: Update to version <IP_ADDRESS>3.g6cf4d40c

'aki' bucket:
75b2c10 (HEAD -> master, origin/master, origin/HEAD) flutter-cn: Update to version 3.13.6

'alkuzad_unxutils-separated' bucket:
00b1359 (HEAD -> master, origin/master, origin/HEAD) Extend Readme

'amorphobia_siku' bucket:
05746b0 (HEAD -> master, origin/master, origin/HEAD) cargo-binstall: Update to version 1.4.1

'amreus_bucket' bucket:
e49d0f8 (HEAD -> main, origin/main, origin/HEAD) ov is now in main buclket

'anderlli0053_AppArchive' bucket:
30e1980d (HEAD -> master, origin/master, origin/HEAD) Updated

'anderlli0053_DEV-tools' bucket:
05ce2a3404 (HEAD -> master, origin/master, origin/HEAD<EMAIL_ADDRESS>Fix hash (Closes #193)

'AntonOks_scoop-aoks' bucket:
952f996 (HEAD -> master, origin/master, origin/HEAD) werf-aoks: Update to version 1.2.263

'aoisummer_scoop-bucket' bucket:
7a1c34a (HEAD -> master, origin/master, origin/HEAD) update bucket

'arch3rPro_scoop-bucket' bucket:
315f8b7 (HEAD -> main, origin/main, origin/HEAD) afrog: Update to version 2.8.8

'batkiz_backit' bucket:
a389186 (HEAD -> master, origin/master, origin/HEAD) dolt: Update to version 1.17.0

'brave-simpletons_scoop-the-business' bucket:
d0ab38b (HEAD -> main, origin/main, origin/HEAD) lens: Update to version 2023.9.290703-latest

'brian6932_dank-scoop' bucket:
9e60819 (HEAD -> master) streamlink-nightly-lean: Update to version 6.1.0-15-g2702c89

'cc713_ownscoop' bucket:
4405ca1 (HEAD -> master, origin/master, origin/HEAD) scoop-directory: Update to version 2023-09-28-16-28-15

'chawyehsu_dorado' bucket:
984e47c7 (HEAD -> master) frpmgr: Add version 1.12.0 (#733)

'chenxiangfang_scoop-chenxf' bucket:
5cf59d9 (HEAD -> main, origin/main, origin/HEAD) clash-for-windows: Update to version 0.20.36

'Cologler_cologler-scoop-bucket' bucket:
21cadc3 (HEAD -> master, origin/master, origin/HEAD) remove tmpwd.json

'danielpauldd_scoop-bucket' bucket:
f6798cc (HEAD -> master, origin/master, origin/HEAD) sslyze: Update to version 5.2.0

'ddavness_scoop-roblox' bucket:
2f877d0 (HEAD -> master, origin/master, origin/HEAD) luau: Update to version 0.596

'deliciousgohan_gohan-bucket' bucket:
c1b6c77 (HEAD -> main, origin/main, origin/HEAD) defold 1.2.192

'dodorz_scoop' bucket:
95fd6fd (HEAD -> master, tag: EDX-<IP_ADDRESS>5, origin/master, origin/HEAD) EDX: Add version <IP_ADDRESS>5

'DoveBoy_Apps' bucket:
854cc294 (HEAD -> master) ffmpeg-shared-nightly: Update to version 110463

'echoiron_echo-scoop' bucket:
1d5a463 (HEAD -> main, origin/main, origin/HEAD) q-dir:11.36

'emulators' bucket:
498719af (HEAD -> master, origin/master, origin/HEAD) ryujinx: Update to version 1.1.1037

'foosel_scoop-bucket' bucket:
164f76e (HEAD -> main, origin/main, origin/HEAD) freecad-weekly: Update to version 34387

'Gladtbam_Bucket' bucket:
56f7aa4 (HEAD -> master, origin/master, origin/HEAD) firefox: Update to version 118.0.1

'gregwen_grewen-scoop' bucket:
3030253 (HEAD -> master, origin/master, origin/HEAD) nodejs: Update to version 20.8.0

'gsminek_dtm-scoop-bucket' bucket:
92d0ab9 (HEAD -> main, origin/main, origin/HEAD) neutrino-*: Update to version 1.3.0.

'hermanjustnu_scoop-emulators' bucket:
408c7869a (HEAD -> master, origin/master, origin/HEAD) ryujinx: Update to version 1.1.1037

'hetingde_Meta' bucket:
f00bf1b (HEAD -> master, origin/master, origin/HEAD) add clash-chinese-patch

'hoilc_scoop-lemon' bucket:
ce1a00cf (HEAD -> master, origin/master, origin/HEAD) rssguard-nightly: Update to version devbuild-110407128

'huangnauh_carrot' bucket:
134e854 (HEAD -> master, origin/master, origin/HEAD) q-dir: Update to version 11.37

'instinctualjealousy_holes' bucket:
f800da6 (HEAD -> master) Merge branch 'master' of https://github.com/instinctualjealousy/holes

'jat001_scoop-ox' bucket:
9db3bf2 (HEAD -> master, origin/master, origin/HEAD) Update apps list on readme

'JSONS' bucket:
fatal: not a git repository (or any of the parent directories): .git

'KnotUntied_scoop-fonts' bucket:
68bfbfa (HEAD -> master, origin/master, origin/HEAD) sudo: Update to version 0.76

'KnotUntied_scoop-knotuntied' bucket:
d630e70 (HEAD -> master, origin/master, origin/HEAD) cpc: Update to version 1.9.3

'LengSword_scoop-yls' bucket:
7fb7391 (HEAD -> main, origin/main, origin/HEAD) gopass: Update to version 1.15.8

'lzwme_scoop-proxy-cn' bucket:
1e9c95274 (HEAD -> main, origin/main, origin/HEAD) Updated at 2023-09-29T01:20:11.924Z

'mo-san_scoop-bucket' bucket:
2718360 (HEAD -> main, origin/main, origin/HEAD) firefox-jp: Update to version 118.0.1

'mogeko_scoop-sysinternals' bucket:
f4ad225 (HEAD -> master, origin/master, origin/HEAD) tcpview: Update to version 4.12

'muggle' bucket:
dc6f486 (HEAD -> master, origin/master, origin/HEAD) chatall: Update to version 1.48.72

'MyScoop' bucket:
b104593f6 (HEAD -> master, origin/master, origin/HEAD) burp-suite-pro-np_fixed: Update to version 2<IP_ADDRESS>

'naderi_scoop-bucket' bucket:
52ea2d40 (HEAD -> master, origin/master, origin/HEAD) waterfox-portable: Update to version 6.0.2

'Nirose_node' bucket:
1af6192 (HEAD -> main, origin/main, origin/HEAD) unchromium: ^117.0.5938.55

'nueko_scoop-php' bucket:
8b0a06d (HEAD -> master, origin/master, origin/HEAD) fix: checkver php7.2-nts

'nuke' bucket:
19bdf17 (HEAD -> master, origin/master, origin/HEAD) winmute: Update to version <IP_ADDRESS>

'ocean' bucket:
ecab644 (HEAD -> main, origin/main, origin/HEAD) parsec: Update to version 150-90b

'p8rdev_scoop-portableapps' bucket:
6782726 (HEAD -> master, origin/master, origin/HEAD) Update

'pleiades' bucket:
490960e (HEAD -> master, origin/master, origin/HEAD) pleiades2023: Update to version 2023-06.20230617

'prezesp_scoop-viewer-bucket' bucket:
7d6f4e3 (HEAD -> master, origin/master, origin/HEAD) [scoop-viewer] Version 0.10.0

'ptbwu_dango' bucket:
6619ccb (HEAD -> master, origin/master, origin/HEAD) v2ray-rules-dat: Update to version<PHONE_NUMBER>08

'rasa_scoops' bucket:
b91b47b (HEAD -> master, origin/master, origin/HEAD) chore: update app index [ci skip]

'rivy_scoop-bucket' bucket:
7aa21a2 (HEAD -> master, origin/master, origin/HEAD) UPDATE zig

'Samiya321_scoop-samiya' bucket:
857049b (HEAD -> main, origin/main, origin/HEAD) chore: update app index

'Scoop_Zapps' bucket:
ed7b8e8 (HEAD -> master, origin/master, origin/HEAD) Auto Update

'ScoopInstaller_Nirsoft' bucket:
4525a70 (HEAD -> master, origin/master, origin/HEAD) Update url list [ci skip]

'ScoopInstaller_Tests' bucket:
4084456 (HEAD -> master, origin/master, origin/HEAD) goneovim-nightly: Update to version nightly-20230929

'shmishtopher_cudnn-versions' bucket:
2197cfa (HEAD -> master, origin/master, origin/HEAD) Add new cuDNN manifest

'ShuguangSun_sgs-scoop-bucket' bucket:
eb5f765 (HEAD -> master, origin/master, origin/HEAD) r-devel: Update to version r85227

'sriramjiyer_PsModuleBucket' bucket:
8187e17 (HEAD -> master, origin/master, origin/HEAD) Az: Update to version 10.4.1

'stxpons_scoop-apps' bucket:
d622181 (HEAD -> master, origin/master, origin/HEAD) PureWriter: Add version 1.5.1 (#69)

'su-u_scoop-bucket' bucket:
26178bb (HEAD -> master, origin/master, origin/HEAD) aa

'TheRandomLabs_scoop-nonportable' bucket:
29a5941 (HEAD -> master, origin/master, origin/HEAD) nodejs-np: Update to version 20.8.0

'tomcdj71_scoop-dev-apps' bucket:
1b6eab8 (HEAD -> main, origin/main, origin/HEAD) composer: Update to version 2.6.4

'tomcdj71_scoop-essential-apps' bucket:
ea2e549 (HEAD -> main, origin/main, origin/HEAD) brave: Update to version 1.58.135

'unoun_scoop-bucket' bucket:
f9a4cec (HEAD -> main, origin/main, origin/HEAD) a5m2beta: Update version to 2.19.0_beta6

'ViCrack_scoop-bucket' bucket:
62ee1a2 (HEAD -> master, origin/master, origin/HEAD) afrog: Update to version 2.8.8

'vidarkongsli_vidars-scoop-bucket' bucket:
0dc68d4 (HEAD -> master, origin/master, origin/HEAD) Update stupidgit manifest

'wangzq_scoop-bucket' bucket:
2fdaf23 (HEAD -> master, origin/master, origin/HEAD) rider202314

'Weidows-projects_scoop-3rd' bucket:
a9d1f47 (HEAD -> main, origin/main, origin/HEAD) encore: Update to version 1.27.0

'wholegale39_onetab' bucket:
40c157f (HEAD -> main, origin/main, origin/HEAD) electerm: Update to version 1.33.26

'WiiDatabase_scoop-bucket' bucket:
f244df0 (HEAD -> master, origin/master, origin/HEAD) inputredirectionclient-qt: Update to version 2.1

'WinApps-share_WinApps-bucket' bucket:
194daea (HEAD -> master, origin/master, origin/HEAD) firefox: Update to version 118.0.1

'x-magic' bucket:
01ed32f (HEAD -> master, origin/master, origin/HEAD) windowsdesktop-runtime-lts-6.0.x-x86: Update to version 6.0.22 windowsdesktop-runtime-lts-6.0.x-x64: Update to version 6.0.22

'ygguorun_scoop-bucket' bucket:
7506613 (HEAD -> master, origin/master, origin/HEAD) WindowTop: Update to version 5.22.2

'yotiky_scoop-bucket' bucket:
f450152 (HEAD -> master, origin/master, origin/HEAD) Remove json files

'yuhaofe_scoop-drey' bucket:
f8704bd (HEAD -> master, origin/master, origin/HEAD) Add manifest: dijo

Scoop Config
aria2-warning-enabled : True
alias                 : @{gui=scoop-gui}
aria2-enabled         : True
last_update           : 29/09/2023 16:11:30
use_lessmsi           : True
scoop_repo            : https://github.com/ScoopInstaller/Scoop
scoop_branch          : develop

PowerShell Version
Name                           Value
----                           -----
PSVersion                      7.3.7
PSEdition                      Core
GitCommitId                    7.3.7
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional Softwares
None

The latest version of CE is 7.5, not 3.5.

The latest version of CE is 7.5, not 3.5.

Indeed it is, i just mistyped, thanks for the correction!

This is the link that is working for me:
https://d1vdn3r1396bak.cloudfront.net/installer/6935791/5259993820145

Anything new with this?

I cannot download the latest version from the official website.

What is the problem here? I could upload the executable somewhere for you if that is the only problem.
Or is it that the link doesn't stay the same? Because the current scoop package doesn't download from the official site either, it's a 7zip that's stored on the ScoopInstaller Github by the looks of it.

I cannot download the latest version from the official website.

What is the problem here? I could upload the executable somewhere for you if that is the only problem.
Or is it that the link doesn't stay the same? Because the current scoop package doesn't download from the official site either, it's a 7zip that's stored on the ScoopInstaller Github by the looks of it.

The only issue now is that the .7z should be repackaged with the current latest version (7.5) and re-uploaded to ScoopInstaller Github repo.

https://github.com/ScoopInstaller/Binary/issues/26


WebApp - Do not show confirmation after performing any transaction with extension account

Describe the bug
Do not show confirmation after performing any transaction with the account connected to the extension
To reproduce the behavior
Version test: https://b9ea25d2.subwallet-webapp.pages.dev/
Steps:

Open the webapp
Connect to extension successfully
Make any transactions with the account connected to the extension
Repeat step 3 then Observe the Approve transaction step

Actual: After clicking Approve transaction, no pop-up confirmation is displayed

The user clicks to close the transaction and will see a confirmation popup

Version test: https://b7767009.subwallet-webapp.pages.dev/
Validation passed


Updated: webcatalog <IP_ADDRESS>

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 83577d317c4d7a2e3c0be3ad24f5a885659311ee

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 73f2f575bed0f939fd5bcb0450353757d460bbcd

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 2c0ee351093b32ebf700cf1e9e43f6bcd7d9fbad

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 2528f30069d14981048f2c3bef0dc14595d4db36

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 3f05f72abd26d6b70895a7f039431f425202b794

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 445c493952841446ce6dd840d53413d42e27805e

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. d92b299e5eec84ac2e1376a21d57d9c049ab9333

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 08aa21ba50cd9fe63f32d4692d8e6bd2701aa7cf

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 8f190194d057f58636bb3d8d559a5160219a62d1

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 06945a6f5211d4838d232910c612457701ab2eb1

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. e70dc93495f48bd2a1f4e38ae2ce1b63b821b216

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 63af7a589c78303172136674b178361641d518df

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 2978cf047b6f82b2990bb93bfe94da14b7788a35

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. 8f1a8440483122435c938cde9217e3d3828dc622

Newer version of webcatalog (<IP_ADDRESS>) is now available in master. c1cb4beac00dbdf3be4937f63b849074439e52d6


After latest fix, now addKmlOverlay() in Ionic with 'file://' is not loading

this.map.addKmlOverlay({ 'url': "assets/overlay.kml" });
This works in 2.3.9 normally, but stopped working when I updated to 2.3.11
I'm working with 'file://' not localhost webviews.

In order to reproduce your issue 100%, please share your project giles on GitHub.

ping

I made another test using this quickdemo and it happens exactly the same. My project is too big now, I think it's better to test in this demo just change the plugin version and try KML page.
In 2.3.9 it works if using 'file://' but not with localhost
In 2.3.11 it works in localhost but not with 'file://'

I think ionic serves the index.html file on http:// always.

I forgot to say that I'm not using 'cordova-plugin-ionic-webview' because of CORS issues, so it shows 'file://' on Origin requests

Thank you for waiting.
I tested the kmlOverlay on file:// with the quick demo, but I have no problem.

Thank you for waiting, I can not confirm your issue.
The KmlOverlay demo of ionic-googlemaps-quickdemo works perfectly even file:// protocol.

I found the problem, I'm using lazy loading so Ionic route works differently. Look at the screenshot:

If you remove all pages from app.module except HomePage and change page title to string in app.components you will see it wont load.

Please create the reproduce demo project, then share it on Github.

I made a fork and this commit: https://github.com/Gabplay/ionic-googlemaps-quickdemo/commit/f111fdc26f30f3d17ab86418eb3c4a43d9a2107b

Thank you for creating the demo project, it's perfect for the inspection.
I fixed the bug. Please reinstall the plugin from the multiple_maps branch.


Feature Request: Option to Honour Semantic Break Lines Without Trailing Space

Feature Requested
Currently the plugin does only recognise semantic breaks if there is a trailing space on the respective lines.
I suggest to offer an option to allow both a [ single ] SPACE\n and a \n after the last identifier -- as per specification no. 4 and 5 -- or word on the line. It makes it fool-proof while writing semantically.
Thank you for considering.
Relevant Screenshot
https://user-images.githubusercontent.com/1460531/169402781-12ee33f1-5838-41eb-8b2f-94cf66b38113.mp4
Checklist

[X] The feature would be useful to more users than just me.

actually, I have thought about it and it makes sense to stich lines back together even if they do not have a trailing whitespace at the end.
so now the plugin will convert them back either way

Thanks!


ObjectListView fork availability

Can you provide some details on where to get the ObjectListView fork from?

I didn't put the fork separately. If you pull down all the files and open in Visual Studio, you'll see two projects. You could delete my main project (FellrnrTrainingAnalysis), leaving just the ObjectListView fork. Alternatively, build everything and just grab the ObjectListView dll file.
I'm hoping my version of OLV is temporary, and the main trunk will be updated to support .NET core 7.
BTW, you can see my changes to the code from https://github.com/FizzcodeSoftware/ObjectListViewRepack as they are marked with "//#!JFS!#"


[DEP-294] Release 2.9.0

Description
SDK Release 2.9.0

Update SDK libraries
Update app version
Update README.md and CHANGELOG.md

References
DEP-294
Testing

[x] Complete 3 steps flow with Zoom liveness.
[x] Complete 3 steps flow with face capture.

Checklist

[X] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[X] All active GitHub checks for tests, formatting, and security are passing
[X] The correct base branch is being used, if not master

Aren't there some new error codes we need to document? 🤔

Aren't there some new error codes we need to document? 🤔

Nope, not for 2.9.0


Add instructions on how to do test app migrations

Previously answered here and here. Just adding this into these docs for future contributors.

Good idea - thanks @lb-!


Add 'Copy Model' context menu option

Made it play a sound, because I'm cool like that

QA Result: Passed ✅

Copy model item is available in the context menu for valid ents with the correct icon ✅
Clicking copies the model path to my clipboard, and plays a sound ✅
Copy model item is not available for invalid ents or players ⚠

I was unable to test this as players don't seem to be right-clickable in the context menu.


Additional Tools

It was suggested you might be interested in some of the tools mentioned here.  I am hoping to find more time to expand on them soon as some of them still need some work to be as useful as I would like.
https://github.com/rshipp/awesome-malware-analysis/commit/f0266011bc2f556c288b4dc3c0796ccc9ca93abe

Thanks @pidydx , I will take a look!

@pidydx GRR is already on the list, the other two(Winjob , MetaFS) I think are not a good fit for this list (not focused at Incident Response)...
But feel free to catch me up in the DFIR slack channel (signup here : https://rishi28.typeform.com/to/sTbTI8)
To talk more on that...

@pidydx can I close this?

No problem!  Ideally I will eventually finish getting those two into GRR anyways for their core DFIR uses sooner rather than later.


feat(ui): optimize status ui behavior

Connecting:

Closed:

Connected:

I feel it might be confused with testing status, how about:

Disconnected: Red carbon:wifi-off, with the tests list fade out
Connecting: Orange carbon:wifi blinking, with the tests list fading in and out
Connected: Nothing, as the network status doesn't matter when everything working normally

Improved by comments


Add cargo-deny to CI to verify licenses and more

Enabled the current permissive licenses that were used but disallowed copyleft licenses. Issues like #319 should not be able to happen again with this, will be detected in the PR and fail the build.
Also enabled some other standard security settings we usually use such as:

Verify no dependencies have RUSTSEC advisories for them for vulnerabilities, unmaintained status and general notices
Disallow bringing in multiple versions of the same crate, to make it leaner and keep compile times good. This can require some tweaking occasionally and in some crate upgrade scenarios temporarily allow ("skip") some crates to have multiple versions of them.

Feel free to tweak and configure deny.toml further, the cargo-deny book has quite in-depth descriptions of it.

Hmm there seems to be some bug or mis-configuration here causing cargo-deny to not detect xcur and fail here as it should (as this branch is before xcur got removed).
We'll have to debug and investigate further, filed https://github.com/EmbarkStudios/cargo-deny/issues/197

Don't you fix that by using the --workspace argument?


🚑  (src/checkboxgroup)-fix warning on tests for theme object

Codecov Report

Merging #145 into development will not change coverage.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           development   #145   +/-   ##
==========================================
  Coverage           86%    86%
==========================================
  Files               20     20
  Lines              550    550
==========================================
  Hits               473    473
  Misses              77     77

Impacted Files
Coverage Δ

src/checkboxGroup/index.js
100% <100%> (ø)
:arrow_up:

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 2c66930...498f026. Read the comment docs.


SQL Server 3-Part Schema Naming

Environment

Elixir version (elixir -v): 1.11.0
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): SQL Server 2017 14.0.3335.7
Ecto version (mix deps): phoenix_ecto: "~> 4.2", ecto_sql: "~> 3.5"
Database adapter and version (mix deps): tds: "~> 2.1", tds_encoding: "~> 1.0"
Operating system: macOS Catalina 10.15.6

Current behavior
SQL Server allows for having separate databases on the same server that are accessible by a [database].[schema].[table] structure. The first element defaults to the database in the connection information, and the second element defaults to dbo.
I am attempting to rewrite some raw string queries referring to a legacy database into Ecto schemas but have been unable to construct the schemas because of a naming limitation.
For example, with a simple query like this:
query = """
select top 5
  GlobalMemberID id
from ref.dbo.ProviderAttribution_ALL
"""

Ecto.Adapters.SQL.query!(Orc.ODS, query)

Making some assumptions, I attempted to create an Ecto schema as
@schema_prefix "ref.dbo"
@primary_key {:id, :text, source: :GlobalMemberID}
schema "ProviderAttribution_ALL" do
end

Unfortunately, I am greeted with an Invalid Object Name error
iex(2)> Orc.ProviderSearch.Attribution |> limit(5) |> Orc.ODS.all()
** (Tds.Error) Line 1 (Error 208): Invalid object name 'ref.dbo.ProviderAttribution_ALL'.
    (ecto_sql 3.5.0) lib/ecto/adapters/sql.ex:683: Ecto.Adapters.SQL.raise_sql_call_error/1
    (ecto_sql 3.5.0) lib/ecto/adapters/sql.ex:616: Ecto.Adapters.SQL.execute/5
    (ecto 3.5.0) lib/ecto/repo/queryable.ex:192: Ecto.Repo.Queryable.execute/4
    (ecto 3.5.0) lib/ecto/repo/queryable.ex:17: Ecto.Repo.Queryable.all/3

If I am connected to the same database and leave it out of the schema with just a schema prefix of dbo or even without, the schema works fine.
The legacy queries join across multiple databases at times, so changing the connection to a particular database is unfortunately not a fix.
Expected behavior
I assumed that I would be able to append the database name to the @schema_prefix such as ref.dbo or have a separate module attribute for the database name of the schema.
Thank you!

@aoswalt The reason why it fails is because we quote the name to avoid SQL injection attacks. We could check if the string has a dot and escape around the dots but this can cause compatibility issues with schemas names with dots in them. Another option is to allow the prefixes to be {"ref", "dbo"}, but I am not sure how much work would be required on Ecto's side.

Here is what I suggest for now, try passing @schema_prefix {"ref", "dbo"} and see where it breaks. If it breaks only on Ecto.Adapters.TDS.Connection, then that's an easy fix and all we need to do is to change said module to escape tuples correctly.

I suggest creating table synonim in database that repo is connected to. Same thing is solution for case where query have to us table from linked server.

Looks like it does just error in Ecto.Adapters.TDS.Connection and Ecto itself doesn't care what type of value it is.
iex(2)> Orc.ProviderSearch.Attribution |> limit(5) |> Orc.ODS.all()
** (FunctionClauseError) no function clause matching in String.contains?/2

    The following arguments were given to String.contains?/2:

        # 1
        {"ref", "dbo"}

        # 2
        "["

    Attempted function clauses (showing 3 out of 3):

        def contains?(string, []) when is_binary(string)
        def contains?(string, contents) when is_binary(string) and is_list(contents)
        def contains?(string, contents) when is_binary(string)

    (elixir 1.11.0) lib/string.ex:2264: String.contains?/2
    (ecto_sql 3.5.0) lib/ecto/adapters/tds/connection.ex:1462: Ecto.Adapters.Tds.Connection.quote_table/1
    (ecto_sql 3.5.0) lib/ecto/adapters/tds/connection.ex:1457: Ecto.Adapters.Tds.Connection.quote_table/2
    (ecto_sql 3.5.0) lib/ecto/adapters/tds/connection.ex:917: Ecto.Adapters.Tds.Connection.create_name/3
    (ecto_sql 3.5.0) lib/ecto/adapters/tds/connection.ex:903: Ecto.Adapters.Tds.Connection.create_names/4
    (ecto_sql 3.5.0) lib/ecto/adapters/tds/connection.ex:899: Ecto.Adapters.Tds.Connection.create_names/2
    (ecto_sql 3.5.0) lib/ecto/adapters/tds/connection.ex:138: Ecto.Adapters.Tds.Connection.all/2
    (ecto_sql 3.5.0) lib/ecto/adapters/tds.ex:136: Ecto.Adapters.Tds.prepare/2
    (ecto 3.5.0) lib/ecto/query/planner.ex:180: Ecto.Query.Planner.query_without_cache/4
    (ecto 3.5.0) lib/ecto/query/planner.ex:150: Ecto.Query.Planner.query_prepare/6
    (ecto 3.5.0) lib/ecto/query/planner.ex:125: Ecto.Query.Planner.query_with_cache/7
    (ecto 3.5.0) lib/ecto/repo/queryable.ex:176: Ecto.Repo.Queryable.execute/4
    (ecto 3.5.0) lib/ecto/repo/queryable.ex:17: Ecto.Repo.Queryable.all/3

@mjaric I had no idea about synonyms in SQL Server, so thanks for that info!
Ideally, it can be translated directly so that I do not have to make any changes to this database we are minimally interfacing with, but that is a good fallback. :)

I found it preferred way over create view alternative. Reason is that when you are creating synonym the object it is referring to don't have to exists.   Neat, right :) ?
Con side of synonym is that you can not set permissions to it, it simply inherit everything from "base" object it refers to which is not the case with view-s.

@josevalim should we support {"ref", "dbo"} for @schema attribute?

Since it seemed like a fairly straightforward change, I made a naive PR for 3-part as well as 4-part naming.

@mjaric that's a bigger change unfortunately so I would keep this exclusively in the prefix handling.

Adding tests to the PR revealed that there is a concern inside of Ecto itself when specifying the prefix inside of a from expression.
The from has a verification that the prefix is a compile-time string.
With part of the test being
Schema
|> select([r], r.x)
|> from(prefix: {"first", "first_schema"})
|> Map.put(:prefix, {"database", "db_schema"})
|> plan()

I get an error of
** (Ecto.Query.CompileError) `prefix` must be a compile time string, got: `{:ok, {"first", "db_schema"}}`
    (ecto 3.5.2) expanding macro: Ecto.Query.from/2
    test/ecto/adapters/tds_test.exs:100: Ecto.Adapters.TdsTest."test from with 2-part prefix"/1
    (elixir 1.11.0) expanding macro: Kernel.|>/2
    test/ecto/adapters/tds_test.exs:102: Ecto.Adapters.TdsTest."test from with 2-part prefix"/1
    (elixir 1.11.0) lib/kernel/parallel_compiler.ex:416: Kernel.ParallelCompiler.require_file/2
    (elixir 1.11.0) lib/kernel/parallel_compiler.ex:316: anonymous fn/4 in Kernel.ParallelCompiler.spawn_workers/7

Is it acceptable to add the functionality to the schema without it working in a from expression, or would it be best to hold off on it?

Go ahead with only trying the prefix in a query. Then once we improve from/join in Ecto, then it will just work here too.


Testing infrastructure plans?

Hey all,
We'd love to explore contributing to this project. Are you planning on rolling out testing in the near term? I think longterm exhausive unit testing is necessary for large-scale adoption?
OpenZeppelin moved to hardhat ~10 months ago iirc and are using mocha/chai.

You can check them here: https://github.com/sushiswap/shoyu/tree/master/test


Workaround for Webpack issue

This implements a workaround for https://github.com/webpack/webpack/issues/11613 that is compatible both with Node.js and Webpack.

I'm more comfortable with https://github.com/microsoft/tslib/pull/129, since this would pollute our wrapper code in a strange, unexplainable way, while that PR gets us closer to just having webpack respect the module entrypoint, as it used to.

Like, I just don't wanna handle two runtimes which do different things with the import using the same code. Moreover, the only reason there's a wrapper is so that in node we only load one copy of the library - in webpack, the module field made sure that one copy was the esm copy. We really just wanna continue that behavior.

Thanks guy! #129 is now merged and deployed


security/acme-client: CA chain still contains X3 CA when the cert was signed by the R3 CA

Let's Encrypt changed its issuer to R3 yesterday. Certificates can still be renewed. But afterwards the CA chain will still contain the X3 instead of the R3 CA.
Our Let's Encrypt plugin imports all Let's Encrypt certificates and CA certificates into the OPNsense trust storage. When doing this the certificate is referenced to the CA by using the caref attribute. However, this attribute is never updated. As a result applications like HAProxy will send an invalid certificate chain, effectively breaking SSL communication.
I'm working on a fix and will provide a workaround shortly.

Workaround / Hotfix
First apply the fix:
opnsense-patch -c plugins f44af645

However, this will not fix existing certs. You have to visit Services: Let's Encrypt: Certificates and forcefully re-issue all affected certificates. This should cause an re-import of the certificate and the CA chain should be fixed.
Don't forget to restart all services that use this certificate afterwards.

OPNsense 20.7.6 includes the fix:
https://forum.opnsense.org/index.php?topic=20389.0
As stated in the release announcement, you have to forcefully re-issue any certificate to fix the invalid CA chain.


Update scalafmt-core to 2.2.1

Updates org.scalameta:scalafmt-core from 2.2.0 to 2.2.1.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: semver-patch

Codecov Report

Merging #167 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #167      +/-   ##
==========================================
+ Coverage   61.34%   61.42%   +0.08%
==========================================
  Files          36       36
  Lines        1203     1203
  Branches        7        8       +1
==========================================
+ Hits          738      739       +1
+ Misses        465      464       -1

Impacted Files
Coverage Δ

core/src/main/scala/laserdisc/protocol/KeyP.scala
92.68% <0%> (+1.21%)
:arrow_up:

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 6765275...67b8703. Read the comment docs.


Remove ExVCR

Summary of changes

Asana Ticket: No ticket.
A bit of a reversion of #463. See that PR for background on what the ExVCR package is and why it was added as a tool as part of our Elixir unit testing. TLDR We tried it as a way to record V3 API responses that happened to be made in the course of unit tests, to prevent problems when the underlying data had changed yet a test expects a certain value.
Ultimately it is probably useful for simple tests. However I (any maybe other devs, I don't know), often ran into problems running the test suite where I would get this error message for tests I was not actively working on or editing:
** (ExVCR.RequestNotMatchError) Request did not match with any one in the current cassette: fixture/vcr_cassettes/[name redacted].json.
     Delete the current cassette with [mix vcr.delete] and re-record.

Which is fine when it happens infrequently... but it happens many times.
In a way the error message exposed a gap in my understanding of how I thought this should work - wouldn't it just append new responses to the existing cassette, ignore it in favor of what's already recorded, or overwrite the recording for me?
From what I can tell, the library has some open issues around cassettes (the recorded responses) possibly not being handled optimally:

https://github.com/parroty/exvcr/issues/72
https://github.com/parroty/exvcr/issues/174
https://github.com/parroty/exvcr/issues/136

And I'm a bit wary that ExVCR might have issues with other tools we use in our testing (see issues for Bypass).
I think part of the problem, is that for some of our tests, including a few we were already using ExVCR to assist with, there are many underlying requests made to the V3 API. For example loading a certain page might load a route with data derived from a query for a schedule which in turn might fetch a trip which then we'll follow up with a request for its vehicle. That's a lot of requests to coordinate, but an hour later that same test is going to fetch a different schedule, ... I'm theorizing that this is a use case that's beyond ExVCR's ability to gracefully handle, but is very common across our entire codebase.
There are other ways to improve our tests - ideally unit tests are isolated to the concept that's actually being tested, without being dependent on the details of the underlying data. Maybe the page load test only cares that there's a %Trip{} being passed to the conn, and we shouldn't test for that by looking for a certain headway text/route name/etc on the page response.
So overall I think it was a nice experiment but ExVCR seemed to be getting in the way more than it was helping. Open to counterarguments on that. This PR deletes everything related to our usage of the library (the :exvcr dependency itself, our own exvcr_helpers module, etc).

General checks

[x] Are the changes organized into self-contained commits with descriptive and well-formatted commit messages? This is a good practice that can facilitate easier reviews.
[x] Testing. Do the changes include relevant passing updates to tests? This includes updating screenshots. Preferably tests are run locally to verify that there are no test failures created by these changes, before opening a PR.
[x] Tech debt. Have you checked for tech debt you can address in the area you're working in? This can be a good time to address small issues, or create Asana tickets for larger issues.

I am very likely not a good match for this PR - I've never used this test directly.


EmbeddedSQL: Support SET variable = expr

Before merging: Please merge https://github.com/AlecStrong/sql-psi/pull/433 first because it contains a commit of it

Sqldelight Idea: if compoundSelect is not null, just use the this and the usual selectquery generator.
If compoundSelect is null, the SET :foo = 42; has to rewritten into SELECT 42;.
@AlecStrong Open question: Rewrite the query in sqldelight or by an embedded sql precompiler? I am fine with both, and could implement it in sqldelight if wanted.

Before merging: Please merge #424 first

Yes, they are host variables. For embeddedSQL you need a precompiler which has access to the host variables and bind these variables into the sql query and write the result into the host variables.
What do you think about a new rule?

Added the host variable rule, nice idea! Works also better with sqldelight class generating

should this still be open as well?
if yes, is sql-psi the right place for it? I assume this isn't ANSI SQL we would want to pass compilation for like SQLite

good question. It is part of the sql standard, but is optional and only available if you have a pre-compiler. And sqlite does not support this precompiler too.
Then we should also revert #420

I see, the fact that its part of the standard but is optional make this difficult. I would opt to not have them in but its because they're very unusual to me which isn't a good reason

Personally, I think the reason to remove this syntax from sql-psi is okay cause it is very uncommon.
Let's create a ticket if somebody else wants this feature too. In the meantime, I will implement this syntax in my db2 dialect.


[macOS] Remove macOS 10.13 related code in the VE repo

Description
Since macOS 10.13 pool have been deprecated, we need to remove all the related code in the VE repo
Related issue: #2960
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos1015, macos11, macos12

/azp run macos1015, macos11, macos12

/azp run macos1015, macos11, macos12


Date focus not available

Bug, feature request, or proposal:
In Angular1 you had onfocus when you click on the field. Is this possible with this version.
What is the expected behavior?
What is the current behavior?
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

Yes, it is. Use the focus event in the input to open the calendar (picker.open()). Please, leave github for bugs report or feature requests. Stackoverflow and similiar services are better avenues to clear up your doubts.

do you have code example. does not seem to be working for me.

Check it over here and close this issue, please: http://plnkr.co/edit/uPNESrA5VbKDrIjP9BaS?p=preview

Thanks. worked great.


[DEP0040] DeprecationWarning - punycode module is deprecated

I used NODE_OPTIONS='--trace-deprecation' to get this stack trace:
[DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:3:9
    at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:392:7)
    at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:328:10)
    at loadBuiltinModule (node:internal/modules/helpers:101:7)
    at Module._load (node:internal/modules/cjs/loader:1001:17)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at Object.<anonymous> (/opt/homebrew/Cellar/markdownlint-cli/0.37.0/libexec/lib/node_modules/markdownlint-cli/node_modules/markdown-it/lib/index.js:14:20)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)

It appears to be coming from markdown-it node_modules/markdown-it/lib/index.js via markdownlint.
see also: https://github.com/DavidAnson/markdownlint-cli2/issues/234 and https://github.com/igorshubovych/markdownlint-cli/issues/437

I used NODE_OPTIONS='--trace-deprecation' to get this stack trace:
[DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    at node:punycode:3:9
    at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:392:7)
    at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:328:10)
    at loadBuiltinModule (node:internal/modules/helpers:101:7)
    at Module._load (node:internal/modules/cjs/loader:1001:17)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at Object.<anonymous> (/opt/homebrew/Cellar/markdownlint-cli/0.37.0/libexec/lib/node_modules/markdownlint-cli/node_modules/markdown-it/lib/index.js:14:20)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)

It appears to be coming from markdown-it node_modules/markdown-it/lib/index.js via markdownlint.
ดูเพิ่มเติมที่: DavidAnson/markdownlint-cli2#234 andigorshubovych/markdownlint-cli#437

Yep, been getting this too.
$ npx -y markdownlint-cli --fix '**/*.md' --ignore 'node_modules'
(node:85059) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.

(Use `node --trace-deprecation ...` to show where the warning was created)

$ node --version
v21.3.0

$ npm --version
10.2.4

Once an updated version of markdown-it is available, I'll publish new releases.

@DavidAnson looks like markdown-it did just (a day or two ago) release their next version that includes this fix: https://github.com/markdown-it/markdown-it/commit/beed9aee2c1b44819afc25d485e86a6c699b6ef0

Yes, that update has already been made to "next" branch: https://github.com/DavidAnson/markdownlint/commit/0e6ffaaab44cc3b229306866f04c991742587b4d

When is next expected to be merged?

I'll probably start a new round of releases in a week or two. This still isn't an issue for an LTS build of Node as far as I know.
https://github.com/DavidAnson/markdownlint/blob/main/doc/ReleaseProcess.md

Is there a workaround to use before the new release?

Fixed in library version v0.33.0.


Add option to set Access-Control-Allow-Origin to echo to request origin

When using CORs with Access-Control-Allow-Credentials:true the Access-Control-Allow-Origin cannot be *. Usual practice is the echo back the the request origin as the allowed origin. It would be good to have some  option to do this rather than having to know the origin ahead of time and add it to the whitelist.

PR #52 adds the option to reflect the origin.
Note that CORS Anywhere should not be used with Access-Control-Allow-Credentials: true, because it would allow other (proxied) domains to see the cookies and other credentials of other proxied domains.

@Rob--W

Note that CORS Anywhere should not be used with Access-Control-Allow-Credentials: true, because it would allow other (proxied) domains to see the cookies and other credentials of other proxied domains.

It's not clear what you meant there.
There seems to be no reason to not set Access-Control-Allow-Credentials: true which requires Access-Control-Allow-Credentials not being *.

@catamphetamine Cookies by browsers are send to a specific domain. When you enable credentials on CORS Anywhere, the cookies set by one proxied site are sent to every other proxied website, because every request from the browser goes to the CORS Anywhere domain. This is a huge security issue, and therefore I strongly discourage the use of credentials with CORS Anywhere.
The only situation where your proposal is acceptable is when your CORS Anywhere proxy is configured to only accept requests to one destination. But that requires more efforts, in particular you need to account for redirects (and strip cookies on redirects, OR not automatically follow redirects).

@Rob--W

Cookies by browsers are send to a specific domain. When you enable credentials on CORS Anywhere, the cookies set by one proxied site are sent to every other proxied website, because every request from the browser goes to the CORS Anywhere domain. This is a huge security issue, and therefore I strongly discourage the use of credentials with CORS Anywhere.

Hmm, I see, so all cookies for multiple proxied domains would end up being set on "CORS Anywhere" domain.
That's a security issue indeed.
Still, if such "CORS Anywhere" instance is configured to only allow proxying a certain origin, there would be no risks involved because an attacker couldn't make it forward HTTP requests to their site to read the cookies.
For example, where you have:
var location = parseURL(req.url.slice(1));

Some kind of an isAllowedOrigin(location.origin) function call could be added (along with the setting).
Another protection from this kind of attacks is configuring originWhitelist so that an attacker would be denied access to a "CORS Anywhere" instance because they can't host a page at such origin.

The only situation where your proposal is acceptable is when your CORS Anywhere proxy is configured to only accept requests to one destination. But that requires more efforts, in particular you need to account for redirects (and strip cookies on redirects, OR not automatically follow redirects).

I don't need any redirects.
I'm fine with redirectless approach.
So, to conclude, there's no valid reason to disallow cookies in this library.


Character "–" is breaking Sublime when it's on LATIN1 plataform

Hello,
We have the same problem as described in this issue:
https://github.com/wbond/package_control/issues/1410
Could you please change this character?
Thank you.

I'll get on it.