Fixes #1387 Fixes #1455 Fixes #1456 - Resource search params

Adds support for more Resource search parameters: https://hl7.org/fhir/resource.html#search

_profile - Profiles this resource claims to conform to (Resource.meta.profile)
_security - Security Labels applied to this resource (Resource.meta.security)
_source - Identifies where the resource comes from (Resource.meta.source)
_tag - Tags applied to this resource (Resource.meta.tag)

That is on top of existing search parameters:

_id
_astUpdated

There are still remaining unsupported search parameters:

_content
_filter
_has
_list
_text
_type

Coverage: 93.69% (-0.005%) from 93.695% when pulling 0610b157540e3819e049d7364a5c17c3adf6d38c on cody-base-resource-search-params into c887281256e738481a90e82742b875983b3570a9 on main.


what is your BTCV test set?

Thanks for your work and code!
Is the BTCV experimental result obtained from the 20 cases official test set? Or obtained from the 12 cases validation set?

It is the 12 casas validation set.


feat(main.go,actions): add command to generate a changelog entry for an individual repo

Fixes #45
TODO:

[ ] documentation changes in deis/workflow

Sample output:
ENG000656:deisrel aaronschlesinger$ GITHUB_TOKEN=$GITHUB_ACCESS_TOKEN ./deisrel changelog individual builder v2.0.0-beta3 8215d19 v2.0.0-beta4 2> /dev/null
v2.0.0-beta3 -> v2.0.0-beta4

# Features

 - 30e7b2f controller: Show the error message from controller instead of resposnse code

# Fixes

 - eacaf38 git-push: handle the errors during git push
 - 8e9de01 cleaner: remove the usage of watch api
 - 9cc7852 gitreceive: ignore error if `git gc` fails

# Documentation

 - d64b400 CHANGELOG.md: update for v2.0.0-beta3
 - d8fe502 badge: added code-beat badge
 - 142b0b7 CHANGELOG.md: add entry for beta4

# Maintenance

 - 6441ece Makefile: update go-dev to 0.11.1

Though not necessarily mentioned in https://github.com/deis/deisrel/issues/45, I'm thinking it might be nice to add some cleanup logic so that when, say, no commits are added for a given repo's changelog under Documentation, then the Documentation block would be removed entirely.  A separate PR for this would be fine; not blocking for this PR.

Since we've been getting better/more disciplined at adding unit tests for PRs in deisrel, could we add some for these changes as well?

@vdice absolutely on both counts. I'll add tests for this code, as well as the ability to omit sections that don't have any entries in them.

Does this handle if the (message) isn't supplied?

@jchauncey you're referring to the abc part of a commit message like: fix(abc): def?

Marking in progress until unit tests are finished

Yeah. Sometimes changes I make affect multiple parts of a repo so the
subsystem part doesn't make sense
On May 11, 2016 5:44 PM, "Aaron Schlesinger"<EMAIL_ADDRESS>wrote:

Marking in progress until unit tests are finished
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/deis/deisrel/pull/47#issuecomment-218622253

@jchauncey in https://github.com/deis/deisrel/pull/47/commits/b1f026e020e20ad16083429446c1627ee54fd8f7, I've added logic to check for commits with no focus. in those cases, the logic inserts a "*"

@arschles thats good for me =)


[WIP] [Not For Merging] Demo automation with pom dep order fixes from PR-780

have this code and #780 both testing in pom-bundle-cleanup branch.. Closing this. Will open a new one when ready.


[Event Request]report 1309 "Standard Sales - Return Rcpt." - OnHeaderOnAfterGetRecordOnAfterUpdateNoPrinted

🕮 Describe the request
Could you please add the following event and include the sender in this event?
trigger OnAfterGetRecord()
begin
    CurrReport.Language := Language.GetLanguageIdOrDefault("Language Code");
    FormatAddr.SetLanguageCode("Language Code");

    if not IsReportInPreviewMode() then
        CODEUNIT.Run(CODEUNIT::"Return Receipt - Printed", Header);
    //+EVENT
    OnHeaderOnAfterGetRecordOnAfterUpdateNoPrinted(IsReportInPreviewMode, Header)
    //+EVENT

    FormatAddressFields(Header);
    FormatDocumentFields(Header);

    [...]
end;

[IntegrationEvent(true, false)] //Include the sender (that we can access our own global variables of the request page)
local procedure OnHeaderOnAfterGetRecordOnAfterUpdateNoPrinted(ReportInPreviewMode: Boolean; var ReturnReceiptHeader: Record "Return Receipt Header")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11755.


Add required attributes to provider config

Fixes: #715

@boz we will have a issue if we configure it only on provider daemon.
Here bid creation will fail when order is configured with required attributes but provider will not have any required attributes as we get provider details from store.

That's fine.  It's just a configuration setting for the provider daemon to filter what it bids on.

If I'm running a demo on testnet I don't want the daemon to bid on orders that have no attributes, for instance.  This would solve that case.

No, bid creation will not work at all if both order and your provider daemon configured with same required attributes

My provider attributes has region:us-west.  1000 orders come in that have have region: us-west.  I have capacity for 10 orders right now and I only want to bid on orders that have team-name: abozanich

An order with zero attributes matches all providers.  I don't want to bid on all orders.  This solves that.

For suppose, a order is created with attributes owner: only-akash and even provider daemon also configured required attribute with same owner: only-akash. shouldBid function will be valid as both attributes are same. So MsgCreateBid will be broadcasted and process will move to handler.go.
When process come to this, this will throw error as order attributes wiill not match with provider attributes. This is because owner: only-akash attribute is not present in provider of chain data.

For suppose, a order is created with attributes owner: only-akash and even provider daemon also configured required attribute with same owner: only-akash. shouldBid function will be valid as both attributes are same. So MsgCreateBid will be broadcasted and process will move to handler.go.
When process come to this, this will throw error as order attributes wiill not match with provider attributes. This is because owner: only-akash attribute is not present in provider of chain data.

@boz , configured from provider daemon. But to fix this issue, we need to add RequiredAttrs field in MsgCreateBid struct.

@akhilkumarpilli this is for an additional filter - it would happen on the provider side after the current order/provider matching.  If the order doesn't match the provider then this additional filter is irrelevant.
Think of it as being similar to a provider daemon that is configured to not bid lower than 100akash on an order - if an order comes in with a max-price of 50akash, then the provider won't bid on it even when the order matches the provider.

additional

True @boz  but the problem is with https://github.com/ovrclk/akash/blob/0a664fcbf64c3d6a0865d680191efcdcff06d59d/x/market/handler/handler.go#L50
If we need this filter, we need to enable this, we need to have this information in order attributes. But, order attributes are all required (for now) and if we don't store this optional attribute on-chain, even our provider will not have the attribute required. So, it won't bid.
One possible solution is, introducing optional attributes on both order and bidding config for the provider


gtk: add Buildable subclassing support

This provides basic Buildable interface implementation support
without the custom_ tags supports
The custom_ parts of Buildable requires providing BuildableParser/BuildableParserContext
which are very C.
As those are not often used by application developers, don't provide them for now.
Part of #56
cc @jsparber

Looks good to me otherwise

Thanks for the review :) I will wait till Julian can give it a try as he has a use case for it in Fractal

works now as excepted :)

works now as excepted :)

thanks for testing :)


Add --target-rid top level option

Closes https://github.com/dotnet/source-build/issues/4413
cc @tmds

@tmds, I think we can get rid of calculation in this repo: https://github.com/dotnet/dotnet/blob/3999c972cc2e8330a922e40a60ca89545756d450/Directory.Build.props#L54 It is only used for runtime where we have this calculation. Besides it's the old logic borrowed from runtime.

@tmds, I think we can get rid of calculation in this repo:

We need this in case the user doesn't specify a rid. This is responsible to make non-portable builds use the rid calculated by init-distro-rid.sh.

Closing in favor of https://github.com/dotnet/sdk/pull/41540.


Add requirements to setup.py

Right now pip-installing delphi is broken because it doesn't pull in dependencies. We need to specify runtime dependencies in setup.py (this will probably be mostly copying from requirements.txt)

assigned to Victor, let's try to make sure we're not duplicating the dependencies in both setup.py and requirements, maybe setup.py can just parse requirements.txt? not sure how to deal with them being split into cuda and non-cuda?

There are ways for setup.py to reference requirements.py, or vice versa, but there are also reasons to not do this. First among them being "development requirements (requirements.txt) and different from runtime requirements (setup.py)". For example, you don't need black or isort to run delphi.
https://stackoverflow.com/a/49684835
The cuda/nocuda split introduces an additional complication. I think the best way to handle this in setup.py is probably with extras_required, though I don't know if there's a clean way to get this to integrate with a specific requirements file.


Update Osiris for cs go please.

Hi, I really like Osiris. It so happened that I still play CS GO on a server where the Kazakhs use cheats and include acting skills. I am also forced to play with WH. But Steam updated GameOverlayRenderer.dll and now Osiris can’t find its patterns, can you please update it for CSGO? Please
And can you tell me if it is updated how to download it from here? I downloaded the required version from another site where there was a DLL version that needed to be injected. How can I find the same version? Otherwise I download it here and don’t understand how to install it

+1

Fixed in ef472aa


Assistants.create() got an unexpected keyword argument 'file_ids'

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

clone the repo, create a new virtual python environment, follow the steps to install the tool

Any log messages given by the failure

2024-04-22 12:46:21,767 - ERROR - _create_assistant - Failed to create new assistant with name: amytest: Assistants.create() got an unexpected keyword argument 'file_ids'
2024-04-22 12:46:21,767 - ERROR - _init_assistant_client - Failed to initialize assistant instance: Failed to create new assistant with name: amytest: Assistants.create() got an unexpected keyword argument 'file_ids'

Expected/desired behavior

be able to create a new assistant.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Windows 11
Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

This is due to latest OpenAI updates and tool probably installs the latest openai library and that causes issue
pip install openai==1.20.0
resolves the issue

New version 0.3.0-alpha has been released for V2 api support.
https://github.com/Azure-Samples/azureai-assistant-tool/releases/tag/v0.3.0-alpha


Add alexandracaulea's file

I added a new post file as requested in #1.
I've created a "your-slide" branch, created "0000-01-02-alexandracaulea.md" file, made a commit, and opened this pull request.

👍 This looks good to me!


yaml indentation error in kubetoy-mcm-application.yaml

line 117  the resources: is  by four spaces to much indented. It is
resources:
requests:
and should be on the same level as requests
resources:
requests:

Thanks for pointing this out!


RF-0.0.3 Visualize the summary of BeSecure OSS projects of interest

Project of interest visualization. this is completed


[docs] CONTRIBUTING.md only yarn is supported

Made the Point - 4 in (## Sending a Pull Request) more user-friendly by making it more elaborative.
Following change is proposed by me for CONTRIBUTING.md :-
{4. Install the dependencies using npm or yarn as shown below:
//for npm
npm  install
//for yarn
yarn install
}

[ ] I have followed (at least) the PR section of the contributing guide.

Only yarn is supported.

Oops , I guess I made a mistake. Sorry about that.
On Sun, 27 Sep 2020, 14:46 Olivier Tassinari<EMAIL_ADDRESS>wrote:

Only yarn is supported.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/pull/22754#issuecomment-699609379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOZGMOUTTJ6XTXPID7OGXF3SH37H7ANCNFSM4R3KNHRQ
.

@Yashvirani No problem, I think that we can leverage this to clarify that npm isn't supported. Thanks for raising

I am glad to contribute !

Thanks @Yashvirani


Polish project accessors

Supercedes https://github.com/gradle/gradle/pull/16538 after rebase

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

@bot-gradle test and merge

Pre-tested commit build failed.

I'm taking care of this. Please don't trigger new builds.

I'm taking care of this. Please don't trigger new builds.

Thanks @blindpirate !

@bot-gradle test and merge

Pre-tested commit build failed.

@bot-gradle test and merge


Update kubernetes go mod deps

What this PR does / why we need it:
Up to date dependencies

This does not seem to work with latest controller-runtime. Closing


Add pinniped_supported_identity_provider_types to the IDP discovery endpoint

Add pinniped_supported_identity_provider_types to the IDP discovery endpoint

lgtm. Should we do the CLI changes in the same PR, or a new PR?

lgtm. Should we do the CLI changes in the same PR, or a new PR?

I'm not really sure exactly how we should translate this into CLI changes at the moment. Right now the best place to use it seems to be in pinniped get kubeconfig help test.

I'm actually not super clear how the CLI could best make use of this information for help text purposes.
The pinniped get kubeconfig command has a flag --oidc-issuer, which can be used to look up discovery information. If that flag is not set, it will inspect the JWTAuthenticator for the issuer. Even then it will only perform discovery if it needs additional information such as which IDPs are available.
Perhaps another way we could make use of the supported IDP types is by checking the --upstream-identity-provider-type against pinniped_supported_identity_provider_types?

Cases that we should make sure are covered:

The issuer is not a Supervisor
The issuer is a Supervisor but the user did not specify any IDP name/type
The issuer is a Supervisor and the user specified an IDP name/type
The issuer is an old Supervisor which does not have the new discovery data
The issuer is a new Supervisor which has the new discovery data
The issuer is a Supervisor using the backwards compatible FederationDomain mode where there are no IDPs listed on the FederationDomain CR
The issuer is a Supervisor using the modern FederationDomain mode where the user lists IDPs on the FederationDomain CR

What else should we consider?


Proposal: parameterize the location of the config file

Pro: could put config file in a non-standard part of the hierarchy.
Con: It seems silly to parameterize both the --decision_file and the --config_file, when one of the main jobs of the config file is to set the location of the decision file.
Work-around: in version 2, the only things config/license_finder.yml has in it are decision_file and gradle_command, both of which can be provided as CLI parameters... That is, the config file doesn't NEED to exist if you remember to pass those parameters to all commands which accept them.
Notes: Maybe this is another indication we should merge the config file and decision file (cc @salimane).  A first pass might be:

Merge the config file and the decisions file; something like:

---
gradle_command: gradlew
project_name: myproj # it's a bit strange to have this in decisions
decisions: [...]

Make --config_file parameterizable, with a default of config/license_finder.yml or even ./license_finder.yml, because not all projects have a config directory.

cc @salimane @beryllium

Other options:

ENV VAR
look in multiple places for a config file (@beryllium - where do you want
to put it?)
once it's used once on the CLI, stick it into a .license_finder
bootstrap-config file (as bundler does once you bundle package once)
use a .license_finder in the root dir to store bootstrap config, put
everything else in the "other file"

I think in any case we're probably overly complicating this ...
On Mon, Jan 5, 2015 at 11:21 PM, Jacob Maine<EMAIL_ADDRESS>wrote:

Another con: you would have to remember to pass --config_file to every
command.
—
Reply to this email directly or view it on GitHub
https://github.com/pivotal/LicenseFinder/issues/131#issuecomment-68824404
.

For my requirements, I need to be able to put in a custom location that hasn't been decided yet. One possibility is {project root}/{vendor}_{project}/collateral/licensing, which is also where the sqlite DB would go ...

With a combination of --project_path, --recursive and --subprojects, it should now be possible to put your config file in one directory, but run license_finder against other directories.  See also #153 and #162.  Closing this proposal.


[Discord-Bot] Integrate Discord Bot with Backend

[x] Integrate /register/ route to receive userHash and return it to user.
[ ] Integrate WebSockets to show the status of the user on discord.

@pandafy can you tell me how to do the WebSockets thing here? We want to show the message through the bot, whenever the user status is changed.


Providing Content for a Named Slot Conflicts With Fallback Content for a Nameless Slot

When providing content for a named slot, if there is any whitespace it will be slotted to the default slot and the default slot's fallback content will not be rendered.
e.g.
@customElement('x-element')
class XElement extends LitElement {
  render() {
    return html`
      <v-slot>
        <v-slot-fallback-content>Test</v-slot-fallback-content>
      </v-slot>
      <v-slot name="other-slot"></v-slot>
    `;
  }
}

<x-element>

Other Content

<x-element>

Empty text nodes will be created and slotted to the nameless slot, preventing the fallback content from rendering.

A workaround would be to assign a name to each slot.


Android not handling POST from iOS during P2P scenario

This is possibly due to a bug in Android. We are not sure yet. @pasin and I have been pair debugging this issue. Tracking ticket - https://github.com/couchbase/couchbase-lite-ios/issues/1447

This seems to be related to POST _changes
This succeeds
## Request
curl -X "GET" "http://<IP_ADDRESS>:5984/ls_db2/_changes?feed=normal&heartbeat=300000&style=all_docs&active_only=true&since=0" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d "{\"active_only\":true,\"feed\":\"normal\",\"style\":\"all_docs\",\"heartbeat\":300000,\"since\":0}"

where <IP_ADDRESS>:5984 is the running Android LiteServ. This does not.
This fails
## Request
curl -X "POST" "http://<IP_ADDRESS>:5984/ls_db2/_changes?feed=normal&heartbeat=300000&style=all_docs&active_only=true&since=0" \
     -H "Content-Type: application/json; charset=utf-8" \
     -d "{\"active_only\":true,\"feed\":\"normal\",\"style\":\"all_docs\",\"heartbeat\":300000,\"since\":0}"

with Socket Closed with remote peer

Using Android (1.3.1-30)

Hi @sethrosetter,
Issue could be same with https://github.com/couchbase/couchbase-lite-android/issues/989 . Fix is already in master.
Don't you mind to retest with 1.3.1-52 ?
Thanks!

I am still hitting the issue with 1.3.1-32

@sethrosetter Thank you for your update.
Dod this issue block you? If so, we can put higher priority.

Note to self:

It seems REST API handler does not meet the recent POST /_changes API changes.

It is causing test failures but besides that is non blocking.


connection pooling

Create a pool of ready connections to reduce connection create time.

@sivukhin i should have put this into draft, just experimenting right now, I opened the or for athos to try it out


add explicit test coverage for util.makeError

Codecov Report

Merging #113 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #113   +/-   ##
=======================================
  Coverage   99.37%   99.37%
=======================================
  Files           4        4
  Lines         963      963
=======================================
  Hits          957      957
  Misses          6        6

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 c17e92f...9ae768f. Read the comment docs.


Get pprof handlers working again

Debug handlers like /debug/pprof/goroutine were broken by #3054; its not particularly obvious how they are supposed to work, as the calls to http.Handle in net/http/pprof/pprof.go actually do longest-prefix matching, so paths like /debug/pprof/goroutine are actually handled by Index().
/cc @juliusv @mark-adams

Whoops! I glossed over that detail in my original PR. I assumed that all of the routes were explicitly declared. Clearly that is not the case. Thanks for the fix! :+1+

@fabxc here you go, I've fix the Index case for prefixes and added a test to ensure we don't break it again.  WDYT?

Cool, thanks 👍


Fix/updating main lockfile removing backend lock

I'm still not making sense of what docker-compose does with all this. Need to understand that before approving...

I totally agree. If we have time, we may want to double-check that docker-compose is aligned with how the root project yarn.lock file works.
Off the top of my head, I am seeing a typescript inconsistency:

We should be using a more recent version of Typescript so that we can use triple-slash directives, which are used by a dependency in the back-end. (see: https://github.com/ubccpsc/classy/pull/249)
I suspect the global Typescript install version was to make bootstrapping and development work quickly, but we may want to sort through the package dependency to ensure that what we put in the main package.json files ends up in the Docker containers.

Also, we upgraded the TypeScript version in one of the repos so that we could fix a Docker-compose build issue that was jamming a container.
I don't think the Docker containers are aligned with the Yarn logic, as after removing the yarn lockfile from the root of the project today, we ran into the same docker compose build issue that was jamming the container build. If Docker was using the same logic as the logic we learned about today, the Docker container build process would still be failing, as we run into the TypeScript error with going the proper way today. Something does not seem right here.

OK, so there are interactions with circleCI - it uses the lock files (both of them, as far as I can tell). More exploring to do...


Build time for libduckdb-sys

I cannot build libduckdb-sys on a MacBook Pro 2019 (Intel i5). It takes around 3-4 mins to build on a MacBook Air 2021 (M1) and MacBook Pro 2021 (M1), but it never finishes in the i5 MacBook, it just gets stuck infinitely. I tried leaving it for more than 15 minutes but it still won't build. Is is supposed to take this long? If so, is there any solution? Thank you.

Could you check the CPU usage during compiling? If the CPU usage is high, then it might just take time
You can download the duckdb lib from their release, don’t use the bundled feature of this repo

For the MacBook Pro (intel i5) it goes up to 85-90% during compiling. How long do you think it will take?

Not quite sure, normally 10 minutes should work…

Does sqlite rust package do something differently? That builds pretty fast in both M1 and Intel Macs for me.

most of the time are spent on build the duckdb c++ code, we don’t add too much extra in this repo. Compare to SQLite,  build duckdb do take more time.
again you can use duckdb rebuild release

Got it, thanks for the help.

FYI related: https://github.com/wangfenjin/duckdb-rs/issues/70

In rusqlite, it is possible to use cargo add rusqlite --features bundled to add rusqlite and bundled sqlite3.lib. Could something be done for duckdb-rs?


Add magic-wormhole

Hey chris! First of all a HUGE thank you and kudos to you! This tool made windows usable for me and a lot of other people.
I was wondering if you already considered adding to the available packages magic-wormhole, I use it a lot to quickly transfer files between machines.
Since it's not present in winutil I just install it using winget, but I think this tool might be worthy of being added as a utility.
Again thank you for all this!

This will be tracked in https://github.com/ChrisTitusTech/winutil/issues/1782 Issue Tracking List, and I've added this program in a recent commit ( https://github.com/ChrisTitusTech/winutil/pull/1795/commits/6f784e2c72e9c3294d5237b0b72ce5c8552ad1e4 ) in this PR
And as always, Thanks for requesting more cool apps 😎 👍

Quick Note: Magic Wormhole is currently outdated in both Chocolatey and WinGet Repos, for the next few days it should be updated in WinGet, See The Update PR in winget-pkgs repo for more info.


Release Kong 2.8.0

Per something I don't quite understand on the gateway end, the Postgres fix was not released in 2.8.1: https://github.com/Kong/kong/issues/8259#issuecomment-1097568845
Continuing this one with the pinned Postgres version.

Per something I don't quite understand on 000
//7the gateway end, the Postgres fix was not released in 2.8.1: https://github.com/Kong/kong/issues/8259#issuecomment-1097568845
Continuing this one with the pinned Postgres version.


TFRobot: Add load subcommand

Is your feature request related to a problem? Please describe
Sometimes deployments are completed successfully but are failed to be loaded from grid, so the deployer cancels them all
Describe the solution you'd like
We need to add a load subcommand and ignore deployments cancelation in case of failure in loading the deployments

WIP:

Added new subcommand to load deployments
Allowed the deployer not to fail on load failure

currently, the loader fails to load the deployments even tho the contracts exists on the chain.
5:39PM INF Loading deployments
5:39PM INF starting peer session=tf-644357 twin=4653
ok: {}
error:
    group_a: |+
        5 errors occurred:
                * failed to find deployment  on node 100: not found
                * failed to find deployment  on node 152: not found
                * failed to find deployment  on node 28: not found
                * failed to find deployment  on node 11: not found
                * failed to find deployment  on node 146: not found

WIP:

the load subcommand now works fine and with no problems

➜  mass-deployer git:(development-add-load-subcommand) go run main.go load -c config.yaml
3:55PM INF Loading deployments
3:55PM INF starting peer session=tf-470410 twin=10804
3:55PM INF twin relay/public key didn't match, updating on chain ...
ok:
    group_d:
        - name: example1vm1
          networkname: example1vm1_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:c0f2:7fbb:8e29:3194:ec2c:b741:d07c
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 310
          contractid: 206126
        - name: example1vm6
          networkname: example1vm6_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:f33a:de91:ae93:cd76:41e5:b3f5:6cb4
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 319
          contractid: 206117
        - name: example1vm3
          networkname: example1vm3_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:d969:30ff:c0a0:bd3e:cc1e:f26a:a3ee
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 324
          contractid: 206120
        - name: example1vm4
          networkname: example1vm4_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:fbed:24f4:7410:4a2d:ef6d:a069:7b5f
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 325
          contractid: 206118
        - name: example1vm8
          networkname: example1vm8_network
          publicip4: ""
          publicip6: ""
          planetaryip: 302:3ad6:c080:7e30:2f01:eff2:8c8f:e621
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 312
          contractid: 206127
        - name: example1vm5
          networkname: example1vm5_network
          publicip4: ""
          publicip6: ""
          planetaryip: 301:36d9:72bc:8ed0:a37a:f34a:be13:c29a
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 317
          contractid: 206119
        - name: example1vm2
          networkname: example1vm2_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:8d78:2520:ba1d:f339:2616:9193:f1f9
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 321
          contractid: 206121
        - name: example1vm7
          networkname: example1vm7_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:8d78:2520:ba1d:ac9:1b99:ec2e:3113
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 321
          contractid: 206116
        - name: example1vm0
          networkname: example1vm0_network
          publicip4: ""
          publicip6: ""
          planetaryip: 301:36d9:72bc:8ed0:9d83:400:aa95:7b5d
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 317
          contractid: 206123
        - name: example1vm9
          networkname: example1vm9_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:fbed:24f4:7410:781c:d54a:138b:b0c9
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 325
          contractid: 206122
error: {}

but the loading after the deployments is not working right, it tries to load deployments from wrong nodes, and when I try to load them with the loader they get loaded successfully

➜  mass-deployer git:(development-add-load-subcommand) ✗ go run main.go deploy -c config.yaml
4:23PM INF validating configuration file
4:23PM INF starting peer session=tf-503074 twin=10804
4:23PM INF twin relay/public key didn't match, updating on chain ...
4:23PM INF done validating configuration file
4:23PM INF starting peer session=tf-503074 twin=10804
4:23PM INF twin relay/public key didn't match, updating on chain ...
4:23PM INF Running deployment Node group=group_d
4:23PM INF Filter nodes Node group=group_d
4:23PM WRN Planetary and public IP options are false. Setting planetary IP to true vms group=example1vm
4:23PM INF Starting mass deployment Node group=group_d
4:30PM INF Retrying to deploy Deployment trial=2 Node group=group_d
4:30PM INF Filter nodes Node group=group_d
4:30PM INF Starting mass deployment Node group=group_d
4:31PM INF Done deploying Node group=group_d
4:31PM INF Loading deployments
ok: {}
error:
    group_d: |+
        9 errors occurred:
                * failed to load network example1vm7_network: could not get network deployment 206165 from node 152: context deadline exceeded
                * failed to load network example1vm1_network: could not get network deployment 206164 from node 260: context deadline exceeded
                * failed to load network example1vm2_network: could not get network deployment 206165 from node 152: context deadline exceeded
                * failed to load network example1vm8_network: could not get network deployment 206181 from node 314: context deadline exceeded
                * failed to load network example1vm3_network: could not get network deployment 206170 from node 260: context deadline exceeded
                * failed to load network example1vm5_network: could not get network deployment 206185 from node 310: context deadline exceeded
                * failed to load network example1vm6_network: could not get network deployment 206183 from node 312: context deadline exceeded
                * failed to load network example1vm9_network: could not get network deployment 206165 from node 152: context deadline exceeded
                * failed to load network example1vm4_network: could not get network deployment 206172 from node 156: context deadline exceeded

4:37PM INF Deployment took 7m45.154755452s

WIP:

converted all loading to be sequential for development purpose.
create a loader function to load deployments using contract ID and node ID
found out the reason of inconsistency in the error messages, it's not because of a bad state, but the LoadDeploymentFromGrid function is not written with large number of requests in mind.
there still improvements can be done, and we need to add the concurrency back

➜  mass-deployer git:(development-add-load-subcommand) ✗ go run main.go deploy -c config.yaml
5:37PM INF validating configuration file
5:37PM INF starting peer session=tf-585473 twin=4653
5:37PM INF done validating configuration file
5:37PM INF starting peer session=tf-585473 twin=4653
5:37PM INF Running deployment Node group=group_d
5:37PM INF Filter nodes Node group=group_d
5:37PM WRN Planetary and public IP options are false. Setting planetary IP to true vms group=example1vm
5:37PM INF Starting mass deployment Node group=group_d
5:39PM INF Retrying to deploy Deployment trial=2 Node group=group_d
5:39PM INF Filter nodes Node group=group_d
5:39PM INF Starting mass deployment Node group=group_d
5:40PM INF Retrying to deploy Deployment trial=3 Node group=group_d
5:40PM INF Filter nodes Node group=group_d
5:40PM INF Starting mass deployment Node group=group_d
5:41PM INF Done deploying Node group=group_d
5:41PM INF Loading deployments
ok:
    group_d:
        - name: example1vm0
          networkname: example1vm0_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:515a:46c8:b649:77be:e1a2:fec4:bee
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 156
          contractid: 87155
        - name: example1vm1
          networkname: example1vm1_network
          publicip4: ""
          publicip6: ""
          planetaryip: 301:3a0b:8af:8f42:e22c:fd6:be83:72e5
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 163
          contractid: 87148
        - name: example1vm2
          networkname: example1vm2_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:3303:8f7f:d117:b383:7771:2cc7:fba9
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 164
          contractid: 87147
        - name: example1vm3
          networkname: example1vm3_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:8161:13c0:130a:8f0:e3b:a83a:854f
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 165
          contractid: 87151
        - name: example1vm4
          networkname: example1vm4_network
          publicip4: ""
          publicip6: ""
          planetaryip: 302:2e79:2383:5add:263f:50d7:814a:f642
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 166
          contractid: 87152
        - name: example1vm5
          networkname: example1vm5_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:515a:46c8:b649:eb57:f09b:9a09:9b21
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 156
          contractid: 87149
        - name: example1vm6
          networkname: example1vm6_network
          publicip4: ""
          publicip6: ""
          planetaryip: 301:3a0b:8af:8f42:6d30:fd25:6e91:c0a5
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 163
          contractid: 87154
        - name: example1vm7
          networkname: example1vm7_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:3303:8f7f:d117:e0d:ecb5:d99f:92d
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 164
          contractid: 87150
        - name: example1vm8
          networkname: example1vm8_network
          publicip4: ""
          publicip6: ""
          planetaryip: 300:8161:13c0:130a:de55:ae15:7dfd:d1c7
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 165
          contractid: 87153
        - name: example1vm9
          networkname: example1vm9_network
          publicip4: ""
          publicip6: ""
          planetaryip: 305:53a:35eb:a6e3:512e:7698:1a39:4c8
          ip: <IP_ADDRESS>
          mounts: []
          nodeid: 181
          contractid: 87157
error: {}

5:41PM INF Deployment took 3m40.547000664s

Work Completed

updated the deployer and loader, and now they load deployments with no problems.
moved the setup function that creates the tfPluginClient to the cmd pkg to create the plugin once for validation and deployment.

➜  mass-deployer git:(development-add-load-subcommand) ✗ go run main.go deploy -c config.yaml
12:42PM INF starting peer session=tf-171856 twin=4653
12:42PM INF validating configuration file
12:42PM INF done validating configuration file
12:42PM INF Running deployment Node group=group_d
12:42PM INF Filter nodes Node group=group_d
12:42PM WRN Planetary and public IP options are false.


Update client to ent v3.1.1

Update client to ent v3.1.1

@zburstein is this still needed? I think it's been obsoleted by recent updates, but checking to confirm.


Add FormulaChannels for composing formula outputs

This PR introduces a channel type called FormulaChannel, which derives from Broadcast channels, and a receiver type for it called FormulaReceiver, which derives from the Broadcast Receiver.
LogicalMeter now returns FormulaReceivers instead of broadcast Receivers,  and these FormulaReceivers can be composed to create new formula engines that operate on the outputs of other formula engines.
This would make it easier to build complex formulas that operate on resampled component data streams.  For example:
net_power_recv = (
    (
        logical_meter.grid_power()
        - logical_meter.battery_power()
        - logical_meter.pv_power()
    )
    .build("net_power")
    .new_receiver()
)

I will add an additional commit with some documentation and usage examples.  If anyone has ideas on how to document,  please feel free to suggest.

Added some documentation and release notes.  This PR should be merged after the formula engine bugfix in #141.

This has been rebased and is ready for review again.


repo2docker not found on PATH

I follow the instruction at https://repo2docker.readthedocs.io/en/latest/usage.html
jupyter-repo2docker https://github.com/norvig/pytudes
But I got a bash: jupyter-repo2docker: command not found

docker info
Containers: 8
Running: 2
Paused: 0
Stopped: 6
Images: 9
Server Version: 18.06.0-ce
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 114
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: d64c661f1d51c48782c9cec8fda7604785f93587
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.93-boot2docker
Operating System: Boot2Docker 18.06.0-ce (TCL 8.2.1); HEAD : 1f40eb2 - Thu Jul 19 18:48:09 UTC 2018
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955GiB
Name: default
ID: 66TB:KSLB:QLIJ:XGMY:6VMK:ZFKS:636A:257S:O5KK:ELYA:L45E:2FEV
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Thank You

Two questions to help debug this:

Which version of repo2docker did you install?
How did you install repo2docker?

This time round I manage to install repo2docker in a Conda env
When I run jupyter-repo2docker https://github.com/norvig/pytudes,  I got this
Docker client initialization error. Check if docker is running on the host. Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))

I had this issue. Restarting my shell worked for me.

Seems like this issue has been resolved. Closing the ticket now.
In general we recommend to post support questions over at discourse.jupyter.org. The forum has a lot more users/viewers than the issue tracker and it is better indexed by search engines. We try and keep the GitHub issue tracker for technical discussions on how to chaneg the software.


Get User Media Return first page

Hi,
When I try to get user all media with getUserMedia method it returns only first page and it is not using nextid.
How can we fix it?
Thanks

I fixed the problem like this.
try handler.getUserMedia(for: "XXXX", paginationParameter: PaginationParameters.maxPagesToLoad(maxPages: Int.max))


TensorflowSharp with Tensorflow-GPU

Describe the bug
I have TensorflowSharp running successfully on CPU; my model gives expected output.
I have Tensorflow 1.14 running successfully locally on GPU using CUDA 10.0 and CUDNN 7.6 (with python).
I would like to run TensorflowSharp on GPU, so replaced the libtensorflow.dll with _pywrap_tensorflow_internal.pyd (renamed to libtensorflow.dll) in 'packages\TensorFlowSharp.1.13.0\runtimes\win7-x64'. I also set the compile architecture to x64.
It loads the dll successfully, however it will always throw a CUDNN mismatch error.
To Reproduce
See above.
Note: I do not have time to create models, train models, create samples from scratch and then adding your 3-4 lines of code to a sample to debug your problem.   You need to provide a complete test case.
Expected behavior
I would figure it would run on GPU fine, since it runs fine from python as well.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

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

Smartphone (please complete the following information):

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

Additional context
Add any other context about the problem here.
I filed this as a bug, however I can see how it is perhaps more so a feature as GPU support is not yet implemented.
Am I missing a DLL reference? The other threads about GPU support don't seem to have encountered this issue.

Got it to work with 10! It's a bug within CUDA, not TF#.
You need to set the ProtoConfig to Allow Growth.
            TFSessionOptions options = new TFSessionOptions();
            unsafe
            {
                byte[] GPUConfig = new byte[] { 0x32, 0x0b, 0x09, 0x33, 0x33, 0x33, 0x33, 0x33, 0x33, 0xd3, 0x3f, 0x20, 0x01 };
                fixed (void* ptr = &GPUConfig[0])
                {
                    options.SetConfig(new IntPtr(ptr), GPUConfig.Length);
                }
            }
            this.session = new TFSession(this.graph, options);

The speedup is amazing!

Got it to work with 10! It's a bug within CUDA, not TF#.
You need to set the ProtoConfig to Allow Growth.
            TFSessionOptions options = new TFSessionOptions();
            unsafe
            {

                byte[] GPUConfig = new byte[] { 0x32, 0x02, 0x20, 0x01 };
                fixed (void* ptr = &GPUConfig[0])
                {
                    options.SetConfig(new IntPtr(ptr), GPUConfig.Length);
                }
            }
            this.session = new TFSession(this.graph, options);

The speedup is amazing!

What do I need to install to run GPU?

Phenix library or sometihgn
Op do 1 apr. 2021 om 06:26 schreef bbhxwl @.***>:

Got it to work with 10! It's a bug within CUDA, not TF#.
You need to set the ProtoConfig to Allow Growth.
        TFSessionOptions options = new TFSessionOptions();
        unsafe
        {

            byte[] GPUConfig = new byte[] { 0x32, 0x02, 0x20, 0x01 };
            fixed (void* ptr = &GPUConfig[0])
            {
                options.SetConfig(new IntPtr(ptr), GPUConfig.Length);
            }
        }
        this.session = new TFSession(this.graph, options);

The speedup is amazing!
What do I need to install to run GPU?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/migueldeicaza/TensorFlowSharp/issues/452#issuecomment-811628524,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQ5OCPZ6UEKZSIHHH2CVSLTGPYXXANCNFSM4IWGKSMA
.


can we import some .dll file in powershell runbook?

In my case, I need to use the Microsoft.WindowsAzure.Storage.dll in powershell.
In local, I can use this command to import this .dll file : [Reflection.Assembly]::LoadFile("D:\Test\2\Microsoft.WindowsAzure.Storage.dll").
Then in the powershell runbook, is it possible to use this .dll file? or any other powershell module can have the same functions like the functions in the .dll?
thanks.

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

ID: 038d927f-2bcc-c62d-b3c3-f194513bced6
Version Independent ID: 41adf2c5-3ab7-7387-e541-89e34aa6a6b1
Content: My first PowerShell runbook in Azure Automation
Content Source: articles/automation/automation-first-runbook-textual-powershell.md
Service: automation
GitHub Login: @georgewallace
Microsoft Alias: gwallace

@imeya Thanks for the Comment. We are actively investigating and will get back to you soon.

@imeya When working with a Hybrid Runbook Worker you control the underlying OS so loading assemblies and dealing with the local file system and working with it is easy.  When working with runbooks that run in Azure, not everything may be available in the sandbox that we run automation runbooks on so things may not always work.
In regards to modules, many modules contain assemblies.. for instance the Azure Storage one does, which loads the assembly you are referring to. And it has logic to load the assemblies when it is loaded..

Thanks @georgewallace for the response.
@imeya We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

https://social.msdn.microsoft.com/Forums/en-US/bc6b7bfc-8274-4a8c-a7c9-e10ddc8ea3fe/how-to-call-c-method-in-dll-from-runbook-in-azure-automation?forum=azureautomation
Assuming you have a "HelloWorld.dll", the first step is to add it to a Zip file.
Within your Azure Automation account, click on: Assets > Modules
At the top of the Modules blade, click on "Add a module".  Another blade will appear, allowing you to upload a Zip file (up to 100MB) from your local computer.
It takes awhile but eventually this Module (aka Zip file) will appear in the Modules blade with a Status of "Available".
What you're not told is that the modules shown there appear in one of two locations within Azure:  C:\Modules\Global and C:\Modules\User   <-- Yours will reside in the latter folder!
The code to execute the aforementioned C# Method is as follows:
Add-Type -Path "C:\Modules\User\HelloWorld\HelloWorld.dll"
[HelloWorld.HelloWorld]::Start()

@sugatmankar , thank you, I will take a try.


Refactor: Offline install

Don't show keyboard upon entering offline install screen
Show blue 'install' button
Trigger install after successful unzip. Currently the user has the option to proceed/cancel install after unzip. At that point I would expect all users to always press proceed, since they have already pressed a button titled Install App

Still work to be done in terms of fully migrating this to the new UI; mostly just wanted to prevent the keyboard from popping up cause that is mad annoying.

Good to merge once conflicts are resolved.


Testing multiple clients with Tesla.Mock

In integration tests, or unit tests for component talking to multiple endpoints, mocking responses from multiple Tesla clients is required.
Example: CRM.Customer.Sync module (in CRM application) uses Foo.Api and Bar.Api, two different Tesla-based clients.
How can it be done with Tesla.Mock?
Another way to achieve is to use mox but it requires declaring behaviors for all API client, and then implement helper functions for bad cases. This is more "right" approach (since other code using API wrapper should not care about actual HTTP response).
Also I understand it's better to refactor the code to isolate interaction, but it's not always possible for various reasons :) Also still using same Tesla.Mock for different components doesn't look right to me.
So.. I'd like to hear about what's possible right now, and thoughts on supporting it, etc.

There are no differences when testing one or multiple clients. You can compose mock functions like:
Tesla.Mock.mock fn ->
  %{url: "http://foo" <> _} -> ...
  %{url: "http://bar" <> _} -> ...
  _ -> {404, [], ""}
end

Thanks a lot for the answer - I see that's possible with single adopter.
(updated the title to cover more questions on tests)
However, for library maintainer, how can I expose this mock behavior correctly? Do you think it's better to use mox in that case?
Example: I wrote ex_force for Salesforce API wrapper. I need to use it from another app (let's say CRM) - and I just want to test different API responses.

Option 1: use Tesla.mock for ExForce in CRM app config - then test code in CRM needs to use Tesla.Mock with actual api responses, which is duplicate from unit test in ExForce, and it is more than CRM
Option 2:  use mox - use mock ExForce Client, so that it does not actually call client

It requires declaring behavior

Also I don't think it's possible to swap adapter with build_client (which I always use). So I'm right now using  using bypass with dynamic client.

In case of a library I'd recommend having a well defined (and spec'd) interface and then use mox to mock on the library level. However, there are sometimes cases when it is easier to mock on the http level - it really depends on the complexity. Recently I had a case of reading a lot of data from multiple different APIs and I went with tape/vcr solution - test again real endpoints and record the responses.
(Very basic implementation of such adapter can be find in the "details" block)

defmodule Tesla.Adapter.Tape do
  @behaviour Tesla.Adapter

  def call(env, opts) do
    dir = opts[:dir] || "test/tapes"
    adapter = opts[:adapter] || Tesla.Adapter.Httpc
    file = Path.join(dir, key(env))

    case read(file) do
      {:ok, {:ok, status, headers, body}} ->
        {:ok, %{env | status: status, headers: headers, body: body}}

      {:ok, {:error, reason}} ->
        {:error, reason}

      {:error, :enoent} ->
        response = adapter.call(env, [])
        File.mkdir_p(dir)
        write(file, response)
        response
    end
  end

  defp key(env) do
    [
      key_method(env.method),
      key_url(env.url, env.query),
      key_body(env.body)
    ]
    |> Enum.filter(& &1)
    |> Enum.join("_")
  end

  defp key_method(method), do: String.upcase(to_string(method))
  defp key_url(url, query), do: String.replace(Tesla.build_url(url, query), ~r/[^a-z0-9]+/i, "_")
  defp key_body(nil), do: nil
  defp key_body(""), do: nil
  defp key_body(body), do: Base.encode16(:crypto.hash(:md5, body))

  defp read(file) do
    case File.read(file) do
      {:ok, data} -> {:ok, :erlang.binary_to_term(data)}
      {:error, :enoent} -> {:error, :enoent}
    end
  end

  defp write(file, response) do
    data =
      case response do
        {:ok, %{status: status, headers: headers, body: body}} -> {:ok, status, headers, body}
        {:error, reason} -> {:error, reason}
      end

    File.write(file, :erlang.term_to_binary(data))
  end
end

Swapping adapter in runtime is possible (see https://github.com/teamon/tesla/issues/219#issuecomment-403280761) but not pleasant nor properly documented :|


Gulp Server for Development

Currently this site does not have a consistent development server. I've used a handful of servers so far but in order to create standard tests we need a standard environment for those tests.
I'm going with gulp based on the target gulp based on the extensive collection of pre-deployment processes that can be automated and robust community documentation. This ties into my overall goal of automating build and deploy.
Notes on deploying the live reload development server are found here

This Dockerfile does not do what you think it does. Failing on
[20:21:12] Local gulp not found in /owls
[20:21:12] Try running: npm install gulp
The command '/bin/sh -c gulp' returned a non-zero code: 1

Thous Shalt Not Commit To Master Without Extensive Testing.

Perform tests on a system for gulp Dockerfiles on a computer that doesn't suffer from \\\ disease (non-Windows please)


Inspector EditorSpinSlider handle no longer works?

Godot version
v4.0.dev.20220118.official [bc5ba38ff]
System information
KDE Linux and Windows 10
Issue description
On 3.x, you can use the slider handle in the editor to adjust values much more quickly, and drag the mouse inside the box (but not on the handle) to adjust finely. In 4.0 this no longer seems to work, you can only do the fine adjustment even though the slider handle is still visible.

I noticed this a few versions ago, and assumed it was just a glitch, but it's always like this now. Is it a useability change maybe, or a bug?  It doesn't work.
It works on all 3.x versions I can remember using.
Minimal reproduction project
No response

Which property exactly is broken?

I remember exponential properties having weird behavior, but some of them are fine, as seen above.

For me, I haven't found a single one that works. That looks to me like the canvasitem rect transforms, and that has the same issue. No matter where I start dragging, it's the slow precise mode.
https://user-images.githubusercontent.com/16022203/150604373-3c1f2d27-f941-41da-bf9b-c48af5d3d678.mp4

Are there any updated on this? I still have this issue on the latest alpha.

I guess these cause by interface/inspector/default_float_step.

Which property exactly is broken?

I remember exponential properties having weird behavior, but some of them are fine, as seen above.

For this case, it's actually a radian value. so the displayed value is converted.

I don't think this is the problem. The step size seems fine for normally adjusting, the issue is that I'm only able to use that step size, and not the alternate I should get when directly dragging the handle (like I can in 3.x)

I don't think this is the problem. The step size seems fine for normally adjusting, the issue is that I'm only able to use that step size, and not the alternate I should get when directly dragging the handle (like I can in 3.x)

The step used may be hard-coded to 0.001, like the properties in #54379.

Is it the same in 3.x? I can't even highlight the handle in 4, which I would assume is a big part of the issue since I can in 3.x and it works fine there.

It may indeed be a hard-coded problem.
PROPERTY_HINT_RANGE exists in 4.0:
https://github.com/godotengine/godot/blob/3639c27cf16cf3ee588c5a1e7587e0deecc9db6a/scene/2d/node_2d.cpp#L415
PROPERTY_HINT_RANGE does not exist in 3.x:
https://github.com/godotengine/godot/blob/b6968ab0602bfe72c71d4efcafe608f9cac36252/scene/2d/node_2d.cpp#L425
This is probably why interface/inspector/default_float_step works in 3.x but not in 4.0.

IIRC, PROPERTY_HINT_RANGE was never implemented for Vector2/Vector3 editors.

I still don't see how this would change what this issue is for. This stuff is could definitely be a problem, but my issue is about the extra handle that allows you to make bigger changes to the value, more like a scrollbar than a slider. Am I just missing something? xD
This is how it should work, and it does in 3.x. I can grab the handle and change the value much faster for big changes, or drag in the box to do it more precise.
https://user-images.githubusercontent.com/16022203/163604368-7f2b3850-444a-4be3-aaf1-a1c53414d7aa.mp4
In 4.x, I can't grab the handle and it changes at the same speed no matter what. The handle also doesn't highlight for me to grab it as it does in 3.x.
https://user-images.githubusercontent.com/16022203/163604478-6765d275-420c-412e-b77f-af7558eb9d43.mp4
Maybe these videos can help explain what I mean

It seems this was possibly fixed around alpha 9, I haven't been able to find by what it was fixed, but I can't reproduce it so far in alpha 9 onward


🐞[Bug]: Unresponsive pages

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Many of the pages that can be accessed through the side nav-bar have an unnecessary extra gap at top
Expected behavior
There shouldn't be such gap
Add ScreenShots

And many other web-pages
What browsers are you seeing the problem on?
Firefox
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@aditya-bhaumik  @sk66641 please kindly check this out

@VijaySamant4368
it seems like it has been fixed in any previous pr


Sort by more than one column

Problem
The orderBy option does not allow you to specify more than one column to sort by. SQL itself lets you specify as many sorts as you want, and performs the sort as expected: sort records by the first column. If any of those values are the same, sort within those records by the second column, etc.
For example, sorting a list of contacts by last name and then by first name: contacts with the same last name will still be sorted alphabetically:
SELECT firstName
FROM contacts
ORDER BY lastName asc, firstName asc

Billy Bob
Aimee Cameron
Kate Cameron
Rob Cameron
John Doe
...

Suggested solution
Allow orderBy to accept an array of columns/directions to sort by which then passes them onto to SQL:
db.user.findMany({ orderBy: [{lastName: 'asc'}, {firstName: 'asc}] })
Alternatives
Some aspects are impossible to replicate: the results of the sorting are taken into account before returning a LIMIT, whcih you can't do outside of SQL—you'd need to return the entire result set and then sort on the client before knowing which records would be included in the cutoff and not.
If limiting isn't a concern, you could manually write some kind of multi-grouped sort that emulates what SQL already does natively.
Additional context
This is basic functionality provided by SQL, I don't a reason to arbitrarily restrict Prisma from using these features.

Thanks @cannikin!
We have this one tracked here as well https://github.com/prisma/prisma-client-js/issues/702
It's on the near term roadmap (that I'm busy putting together so we can publish it, stay tuned!) so something we'll likely support soon (think within 1-3 months, the sooner the better).

I'll thus close this issue in favor of this other one.
Thanks


Score Display Background Issue

Hey Guys,
We should take a look at the score_display handling.  I added a background animation in my YAML that works great with one player, but as soon as you add another, the background animation disappears.  Just wanted to get this into the tracking system before I forget about it.  :)

This has been resolved


fix(portal): Prevent races during relay selection by only using the ones connected for more than 5 seconds ago

Closes #6099
Should push #6109 to not being needed short term.

@jamilbk we need to wait for 5 seconds in integration tests now.

Is 5s enough? If you look at the logs in https://github.com/firezone/firezone/issues/6099#issuecomment-2259784744 in detail, you can see that the same relay that is returned in disconnected is still given out later as a connected one. And the logs are minutes apart there.
My Elixir isn't very good 😅
Is this definitely fixing the race condition where a disconnected relay is never returned as connected?

@thomaseizinger @jamilbk race condition is fixed separately in this PR, when we select for new relays we exclude the ones from disconnected_ids from the query.

@jamilbk

One thought that came to mind here was if we roll over Relays too quickly, but I guess the region deployment strategy should prevent that, i.e. one instance in each region is rolled.

We only shut down instance when new one is healthy, there is a timeout that we give before we fire a liveness probe which should be more than enough to cover the 5 seconds difference. As we scale and have 3+ relays per region this won't be an issue at all because we'll migrate them one by one.

@thomaseizinger @jamilbk race condition is fixed separately in this PR, when we select for new relays we exclude the ones from disconnected_ids from the query.

And that helps across multiple relays_presence events? I've also seen disconnected relays returned as connected in later events.

@thomaseizinger @jamilbk race condition is fixed separately in this PR, when we select for new relays we exclude the ones from disconnected_ids from the query.

And that helps across multiple relays_presence events? I've also seen disconnected relays returned as connected in later events.

Look at relay 542b5b7b-ba09-4573-af81-43614a94d6c0 in the linked logs. It is being returned minutes after as connected in presence events for different relays, despite already being disconnected.

And that helps across multiple relays_presence events? I've also seen disconnected relays returned as connected in later events.

From the logs it looks like 542b5b7b-ba09-4573-af81-43614a94d6c0 was connected, then it disconnected and connected back (and stayed like that). The only issue with logs is that we had it once in connected and disconnected list once (due to nature of using CRDT for distributing presence that Phoenix aggregates over a time window, ~1.5s for inter-cluster events).
I think the reason for this was that the relay that was connected to an API instance re-established a websocket connection to a new API instance because everything is rolled out at the same time. With current changes if it jumps between instances disconnect message will come really quickly but it will be visible in connected only after 5 seconds (that are only sent when relay client/gateway uses is disconnected so not pushed proactively). This also will help if we have a relay that crash loops - it won't be able to spam websocket processes and hurt the connectivity.

And that helps across multiple relays_presence events? I've also seen disconnected relays returned as connected in later events.

From the logs it looks like 542b5b7b-ba09-4573-af81-43614a94d6c0 was connected, then it disconnected and connected back (and stayed like that). The only issue with logs is that we had it once in connected and disconnected list once (due to nature of using CRDT for distributing presence that Phoenix aggregates over a time window, ~1.5s for inter-cluster events).

Will the relay ID change when its stamp secret changes? These IDs need to be unique to the relay's state (available allocations, stamp secret etc). So when it reboots, it needs to be treated as a different relay, otherwise I have no way of knowing in connlib, whether or not I need to throw away the state I have or can keep using it.

@thomaseizinger relay id will change if IP address will change, relay should keep stamp_secret between WS reconnects so we should be fine?

@thomaseizinger relay id will change if IP address will change (so new VM has new ID), relay should keep stamp_secret between WS reconnects so we should be fine?

It keeps the secret when it reconnects but not if the container restarts. So that could be an issue.

@thomaseizinger relay id will change if IP address will change (so new VM has new ID), relay should keep stamp_secret between WS reconnects so we should be fine?

Can you make it based on stamp secret instead? I can move the secret to the URL if that helps.

So when it reboots, it needs to be treated as a different relay, otherwise I have no way of knowing in connlib, whether or not I need to throw away the state I have or can keep using it.

Just realized, why do you need to worry about it? You are guaranteed to get presence event when that happens, when you get one you should always discard all state related to it, doesn't matter if will reboot as the same one or not. Or I am missing something?

So when it reboots, it needs to be treated as a different relay, otherwise I have no way of knowing in connlib, whether or not I need to throw away the state I have or can keep using it.

Just realized, why do you need to worry about it? You are guaranteed to get presence event when that happens, when you get one you should always discard all state related to it, doesn't matter if it will reboot as the same one or not. Or I am missing something?

If it is a relay that I already know, I must not throw away the state because the relay identifies me by my 3-tuple so it won't give me another allocation if I previously already made one.
I identify the relay by its ID and keep the local state if I already know it.

If it is a relay that I already know, I must not throw away the state because the relay identifies me by my 3-tuple so it won't give me another allocation if I previously already made one.

Would it currently return an error if you try to get another allocation? Would it be better to either return existing allocation or remove old one and create a new one if the same peer (3-tuple) is requesting a new one vs keeping the state even after it's ID being in disconnected_ids?

If it is a relay that I already know, I must not throw away the state because the relay identifies me by my 3-tuple so it won't give me another allocation if I previously already made one.

Would it currently return an error if you try to get another allocation? Would it be better to either return existing allocation or remove old one and create a new one if the same peer (3-tuple) is requesting a new one vs keeping the state even after it's ID being in disconnected_ids?

Yes, creating an allocation when you already have one is an error. It would be a deviation from how TURN Is meant to work. I am not against doing that but to me, that is a bigger chunk of work because we need to think through attack scenarios etc. There is probably a reason why the TURN protocol is specified the way it is and I would like to stick to it for the time being unless we have good reason to change this.
In this particular case, it seems reasonable to me that a relay ID is unique per stamp secret. When the stamp secret changes, the credentials change too, meaning semantically, it is a new relay. Other than the same IP, it has nothing in common with the previous instance. All the state management gets a lot easier if we just treat it as a new relay.
If you read through https://github.com/firezone/firezone/pull/6101, you'll learn that exactly this upsert behaviour is the underlying cause for the busy loop that we have been experiencing.

@thomaseizinger do we also want relay to be created when the same relay reconnected with the same stamp secret?
The reason why I'm asking all this is that if we start to create new relays on every stamp secret change there will be much more of them, so it will be really easy to spam our relays table with entities. Fortunately we don't enable self-hosted relays feature for anyone so it can only happen by an accident, but who knows how this will change in a year or two.

@thomaseizinger do we also want relay to be created when the same relay reconnected with the same stamp secret?
The reason why I'm asking all this is that if we start to create new relays on every stamp secret change there will be much more of them, so it will be really easy to spam our relays table with entities. Fortunately we don't enable self-hosted relays feature for anyone so it can only happen by an accident, but who knows how this will change in a year or two.

Good question. A reconnect with the same stamp secret means all the state on the relay is intact and we just had a network partition of the WebSocket.
Thinking about though, if there is a network partition, we would have also broadcast a relays_presence, signalling that relay as disconnected and thus cleared all local state. Even if it reconnects with the same secret, we would have lost our local state already.
So I think what I need to do locally is react to the AllocationMismatch error, send a REFRESH with lifetime 0 (that deletes the current allocation) and start again.

I have a solution ready that fixes this on the connlib side: https://github.com/firezone/firezone/pull/6117. With that, we don't care how you generate the relay ID and what it is correlated to.
For now, I am also assuming that the credentials don't change. If I already know the relay with a certain ID, I don't do anything to it.
This is based on the assumption that we will always receive a relays_presence event when a relay disconnects, regardless whether it reboots, meaning we would have already thrown away the state anyway prior to that so there is no need for upserting and we just need to sync up the state with the relay by deleting the allocation and making a new one in case it only got partitioned and not restarted.


RFC: rw (or a variant) should be able to rewrite under binders

Proposal
The triage team rejected #5994 and thought that it would be better if rw had the ability to rewrite under binders, probably by reusing some of the internals of simp. See the discussion there.
Impact
Add :+1: to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add :+1: to it.

Isn't this simp_rw?

It's what simp_rw tries to be a substitute for, but it doesn't turn side-conditions into new goals, and (I assume) it can loop if the rewrite rules loops.
And from a UX pov, it seems desireable for there just being one tactic that works (or fails with a good error message), rather than sending every new issue with “motive not type correct” to despair (or to Zulip), doesn't it?

I added a clarifying sentence in the RFC.

(Rough notes left for a future implementors) One difference to simp_rw is that the rw envisioned here would be (like the current rw) a simultaneous rewrite of (equal) occurrences, which is sometimes presumably different from simp_rw. Possibly the new rw would use a conv-like strategy to go underneath the innermost binder and then do the existing rw.

RFC accepted!


Remove screenshots

This needed because names of images were changed

@savvinsergey,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Coroutine

coverage: 84.998% (-0.1%) from 85.107%
when pulling fa84bb298c84a3e92ecdcf9053934aedbd88986c on coroutine
into 27b48d5cb6e7538356494a41e70f1f549819847b on main.


Fix make_dask_array with roi

Fix extracted from #1159 - fixes #933
Contributor Checklist:

[N/A] I have added or updated my entry in the creators.json file
[x] I have added a changelog entry for my contribution
[N/A] I have added/updated documentation for all user-facing changes
[x] I have added/updated test cases
[N/A] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed

/azp run libertem.libertem-data

Looks good, merging! :-)

Looks good, merging! :-)


BUG FIX: Mutation of property can output as an array

Bug found where changing a property that was already set either by deserialization or property set.
On serialization, will be output as an array of values.
Corrects the SetValue property and adds test in serialization exercising a property change.

https://www.nuget.org/packages/Ical.Net/4.2.0


Stochastic Gradient Descent in case of multiple local minimums

As I was reading the article it came to me that in some cases where multiple local minimums exist, how do we find out what combination of W and b lead to the global minimum?

@mengchantang This is a great theoretical question. The most accurate answer is that - as with all optimization approaches to complex multi-dimensional problems - we don't really know! The simple practical answer is that proper regularization usually helps us avoid this problem. The intuition is that the simpler the model, the more likely it will find the 'true', most simple solution - which usually corresponds to the global minimum.


Incomplete setup

Describe the bug
While setting up the env for the training lab. (Solutions/Training/Azure-Sentinel-Training-Lab/Modules/Module-1-Setting-up-the-environment.md) it shows that the watchlists are being added. This is not the case when the env is set up.
You'll need to manually add the HighRiskApps.csv file, which I didn't really find somewhere on this repo.
To Reproduce
Steps to reproduce the behavior:
Setup sentinel in Azure
Select the workspace of your choice as sentinel test enviroment
Search Azure Sentinel Training Lab (preview)
There is no step to add watchlists. The watchlist HighRiskApps is necessary in Module 7, Exercise 1 step 13.
Expected behavior
I would expect that the watchlist was added when setting up the enviroment.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: W10
Browser: FIrefox

Issue was solved by a PR from myself


fix call to rma proc method

fixed call to rma_type method.
made easy rot stub/overwrite
some small method name changes

Task linked: CU-2yyynp9 Another shipment that is missing from Andlor


Unify GraphQL fragments

What I observed is that we create a bunch of duplicated GraphQL code.
It would be nice to split code into more reusable fragments.
Ref:

#5279
#5280

@vikiival Can you clarify a bit more what needs to be done here?


Lost encoder.pth in mono_1024x320

Thanks for your work! @zxcqlf
It seems that the encoder.pth is not included in here

Note that please use evaluate_depth.py for 640x192 models and evaluate_hr_depth.py --height 320/384 --width 1024/1280 for the others. See evaluate_hr_depth.py and networks/nets.py for more details!

The habitual thinking from monodepth2 misled me.
Thanks for your reply!


Integration Test - Release - 2018/08/17 02:53:13

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest3 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


mysql_fetch_assoc not showing

A small thing but.
The mysql_fetch_assoc doesn't show up as a hint, but all the other fetches do, like  mysql_fetch_array
while($row = mysql_fetch_assoc($query))

I am looking at this. . It seems to be a bug in how I am reading in the syntax strings.

lol it turns out it was a major flaw in how I was parsing the function config files. There were dozens of hints being dropped not just mysql_fetch_assoc.
Thanks for catching this. . I will have a fix out shortly. It might be a couple of days as I am travelling this week.


build: pybind11 raise min to 2.7 and make self-builder

Any concerns? Is anybody under constraints to use pybind11 older than 2.7, which was released back in 2021?
And apologies, the original headline on this PR said "2.12", but it was wrong -- the minimum is being raised to 2.7, but 2.12 is the version we'll build automatically if requested and it's not found externally.


Create codeql-analysis.yml

Testing GitHub's code vulnerability scanner.

No need to merge to test it ...

Does not work at all ...


shared: Add TypeScript build step

This transpiles the JavaScript and (future) TypeScript in static/shared/js to static/shared/lib. It also compiles away ES2020 syntax that’s not supported by the oldest JS engines targeted by zulip-mobile.
Discussion: https://chat.zulip.org/#narrow/stream/48-mobile/topic/.40zulip.2Fshared.20building/near/1410166

Thanks!
There are two key workflows we use the shared package in for mobile, so these are where I'd like to do some workflow development to make sure that we continue to have a good workflow:

Developing changes. The big thing here is that one just hits save in the editor -- including to source files in the shared package -- and then the app updates, with no need to go run another command and wait seconds (or longer) for a build step.
This is accomplished with yarn link: https://github.com/zulip/zulip-mobile/blob/main/docs/howto/yarn-link.md

Building and publishing new versions of the shared package: https://github.com/zulip/zulip-mobile/blob/main/docs/howto/shared.md#publishing-zulipshared-to-npm

Then in the future when there's actual TypeScript involved, there's a third thing we'll want to work out:

Running TsFlower on the generated .d.ts files, to produce .js.flow files.

That can happen lazily, though. Before we do that, if we want we can always keep writing/updating .js.flow files by hand -- that's the status quo already, in any case. The TypeScript migration just introduces an opportunity to do better, not a regression.

Developing changes. The big thing here is that one just hits save in the editor -- including to source files in the shared package -- and then the app updates, with no need to go run another command and wait seconds (or longer) for a build step.

I expect the only additional step here will be to run tsc --watch in the shared directory.

Building and publishing new versions of the shared package: https://github.com/zulip/zulip-mobile/blob/main/docs/howto/shared.md#publishing-zulipshared-to-npm

I expect this workflow will not change, since npm publish automatically runs the prepare script.

I expect the only additional step here will be to run yarn tsc --watch in the shared directory.

Cool. I think validating that expectation, and writing the corresponding updates to the instructions, is the main thing we need to do, then.

Let me know when this PR is ready for me to review.

It'd be slightly cleaner from an upgrading perspective if the first release that added lib/ didn't yet remove js/ from the release artifact

Okay, I’ve separated those steps as two commits. Feel free to merge and insert a release commit between them if you’d like.

Okay, I’ve separated those steps as two commits.

Great, thanks.

Feel free to merge and insert a release commit between them if you’d like.

Happy to do this except it sounded above like @timabbott wanted to review as well.

lgtm; @gnprice feel free to process this.

I tried npm publish --dry-run after the first commit (plus npm version patch), and it didn't include the desired lib/ directory:
$ npm publish --dry-run
npm notice
npm notice 📦<EMAIL_ADDRESS>npm notice === Tarball Contents ===
npm notice 1.2kB README.md
npm notice 613B  icons/bot.svg
npm notice 450B  icons/ellipsis-v-solid.svg
npm notice 768B  icons/gif.svg
npm notice 3.1kB icons/globe.svg
npm notice 651B  icons/language.svg
npm notice 503B  icons/mute.svg
npm notice 339B  icons/README.md
npm notice 5.5kB icons/readreceipts.svg
npm notice 7.3kB js/fenced_code.js
npm notice 1.8kB js/internal_url.js
npm notice 709B  js/internal_url.js.flow
npm notice 6.9kB js/poll_data.js
npm notice 1.3kB js/poll_data.js.flow
npm notice 1.6kB js/resolved_topic.js
npm notice 348B  js/resolved_topic.js.flow
npm notice 5.4kB js/typeahead.js
npm notice 698B  js/typeahead.js.flow
npm notice 4.5kB js/typing_status.js
npm notice 442B  js/typing_status.js.flow
npm notice 364B  package.json
npm notice 604B  tools/npm-postversion
npm notice 209B  tools/npm-version
npm notice 757B  tsconfig.json
npm notice === Tarball Details ===
…

On investigating, from https://docs.npmjs.com/cli/v9/commands/npm-publish I think the issue is that without a files field the NPM tools look at .gitignore and exclude the lib directory because it's ignored there.
I'll try fixing that.


Insert Embedded Struct for AsChangeset

Will diesel support #[diesel(embed)] on AsChangeset structs? Would be nice for reuse between Insertable and "update-able" structs.

This would be really cool integrated into diesel.  In the meantime I happen to do exactly this in a macro I wrote and your welcome to come check it out.   link-to-macro

Will diesel support #[diesel(embed)] on AsChangeset structs?

Yes. I just haven't gotten around to implementing it. IIRC the last time I worked on it, there was a weird interaction between treat_none_as_null = "true" and embed on an Option field that I wanted to think about. Feel free to open a PR for this, though.

Hello, how is the status of this feature ?. I could try to work on it if nobody does right now.

@vnghia That's not implemented yet, but we would be grateful to receive a PR for this.
You can find the code for the derive here: https://github.com/diesel-rs/diesel/blob/09d5e1050a40d698b10af98bd10495c98ccfaa7f/diesel_derives/src/as_changeset.rs
The Insertable derive already supports the embed attribute: https://github.com/diesel-rs/diesel/blob/master/diesel_derives/src/insertable.rs
You might be able to use that as blue print for how to approach the implementation.


Help to RUN this GUI Downloader

Hi,
I am new to GIT so can someone please help me to run this downloader.
how to run this.
What are the requirements to run this.

What OS are you using? I'm on Fedora 36 and I cannot get it to run even with the one file set to execute as a program. Is there something I'm missing? I've gotten this issue on other Cyberdrop downloaders supposedly usable on Linux.


"Glodeanu Sărat" is listed in the drop-down menu

Description:
"Glodeanu Sărat" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Glodeanu Sărat" in the search bar.

Expected results
The location is listed in the drop-down menu as "Glodeanu Sărat, Buzău".


SCM panel is stuck

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T18:07:25.676Z)
OS Version: Windows_NT x64 10.0.10586
Extensions:

Extension
Author (truncated)
Version

markdown-toc
Ala
1.5.6

vscode-database
baj
1.2.0

vagrant
bbe
0.5.0

vscode-standard-format
che
0.0.12

vscode-standardjs
che
1.1.8

npm-intellisense
chr
1.3.0

gitignore
cod
0.5.0

vscode-markdownlint
Dav
0.10.0

githistory
don
0.2.3

xml
Dot
1.9.2

gitlens
eam
4.4.3

vscode-npm-script
eg2
0.2.0

git-project-manager
fel
1.4.0

vscode-npm
fkn
3.3.0

vscode-auto-open-markdown-preview
hnw
0.0.4

beautify
Hoo
1.1.1

mysql-scratchpad
jbl
0.1.1

plantuml
jeb
2.1.3

markdown-table-formatter
jos
0.2.3

vscode-github
Kni
0.18.1

VS-code-vagrantfile
mar
0.0.5

vscode-remark
mrm
1.1.0

debugger-for-chrome
msj
3.2.0

mysql-inline-decorator
odu
0.0.4

vscode-docker
Pet
0.0.16

java
red
0.9.0

vscode-sql-beautify
sen
0.0.4

markdown-pdf
yza
0.1.7

vscode-open-in-github
ziy
1.2.7

Steps to Reproduce:

Open multiple VSCode windows on different projects
Make changes in one of them (whether these changes are from within VSCode or using another editor does not matter)
SCM panel does not reflect changes. Refresh button does nothing <<< This is not 100% reproducible & sometimes it happens right after a full VSCode restart

Reproduces without extensions: No... but at this issue is not 100% reproducible, I am unsure about the problem solved is due to restarting or disabling extensions.

Can you reproduce on another machine?
Does the file explorer update if you add new files to a visible folder?

I only have a single windows machine. I will test file addition from another source than vscode next time I face the problem.

I forgot to mention one thing I did to trouble-shoot. Once, restarting VSCode did not fix the issue. Going in the Windows task manager showed that there were multiple background VSCode processes, even after the UI was closed. Killing those background processes & restarting VSCode fixed my problem.

Alright, good to know. Let me know if this happens often.

I reproduced it today. Killing the background task that was taking 15%-20% of CPU produced the following in the UI window: Extension host terminated unexpectedly. Please reload the window to recover.

So my issue is very likely due to one of the extensions. Now I/wee need to understand which one...


The response is not formatted (json/html)

Details
❗  After some debugging, I found that the body is truncated, probably the payload is too big. ❗

I have both installed jq and prettier any clue?
debug info
[INFO  Wed Mar  6 13:52:12 2024] ...utils.lua:19: hurl: request finished
[INFO  Wed Mar  6 13:52:12 2024] ...utils.lua:19: Detected content type: application/json; charset=utf-8
[INFO  Wed Mar  6 13:52:12 2024] ...utils.lua:19: formatting body with json
[ERROR Wed Mar  6 13:52:12 2024] ...utils.lua:30: formatter failed4

Checklist

[ ] lua/hurl/utils.lua
[ ] lua/hurl/main.lua

I have the very same issue, moreover ever the 'headers table' is getting truncated too.

Thank you @Viroide for your report. It's failed on the format process: formatter failed4. I will try to reproduce the issue sometime this week. PR's welcome if you could reproduce the issue on your own.


Illuminate\Pagination\AbstractPaginator must implement the according Contracts interface.

Also there must be one pagination interface in Database library
Abstractions fixes - pagination length aware context, interfaces completeness and logic.
Problems related to the proposed pull request:

Illuminate\Pagination\AbstractPaginator was actually length aware because it was using $this->hasMorePages(), which is a length aware method. If Illuminate\Pagination\AbstractPaginator does not implement Illuminate\Contracts\Pagination\Paginator, this method is undefined at all in abstract class. Maybe the methods hasPages(), hasMorePages() must be moved from Illuminate\Contracts\Pagination\Paginator and Illuminate\Pagination\AbstractPaginator to the according LengthAwarePaginatorS as length aware method.
Adding "implements Illuminate\Contracts\Pagination\Paginator" construction adds to Illuminate\Pagination\AbstractPaginator another one indirectly length aware method - nextPageUrl() - it's implementation in Illuminate\Pagination\LengthAwarePaginator suppose the idea of lastPage() method. This method has to be rewritten in Illuminate\Pagination\AbstractPaginator to ignore length aware context.
Illuminate\Pagination\AbstractPaginator has no setCurrentPage() method, but it has everything for it, and AbstractPaginator nature, whether length aware or not, suppose this method to exist, so setCurrentPage() should be moved to Illuminate\Pagination\AbstractPaginator from Illuminate\Pagination\LengthAwarePaginator. Moreover, this method has object context and it's name suppose protected property currentPage to be set, but instead it does not do this and works as a static method. It is not the expected setter behaviour. This method suppose to return void, but I have left the signature unchanged for backward compatibility.

An length aware paginator means the paginator knows the total count, and thus can tell us which page is the last page. The hasMorePages does not indicate that the paginator is length-aware, just that it knows there are more items. This is done my the simple paginator by selecting $pageSize + 1 items, and check if it gets that extra item. If that is the case, then there exists at least one more item and the Next page button can be rendered.
I agree that there are problems in the code structure around the paginators, but moving the hasMorePages method to the LengthAwarePaginator contract seems wrong. Should it perhaps be an abstract method in the AbstractPaginator?

Lots of breaking changes on the 5.5. branch for no user benefit.


No audio in DND mode

If I set my android phone to DND mode I can't hear anything if I start a call.
I think there is a workaround for this since other phone applications don't do this.
Would be great if you could fix this :) Great app BTW

Please open this issue in baresip-studio project.


Generated protobuf code for oneof type doesn't comply with documentation

What version of protobuf and what language are you using?
Version: Protobuf compiler 3.6.1
What did you do?
I am writing a client in golang that talks to a server(written in C++) using protobuf messages.
Generated code for our protobuf message definition containing a oneof field doesn't contain a type interface as explained in the example provided here - https://developers.google.com/protocol-buffers/docs/reference/go-generated#oneof
What did you expect to see?
A type interface to identify which of oneof member is set.
What did you see instead?
A member for each of oneof fields in the generated struct. But no type interface.
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment?
Our server application that processes protobuf request is in C++.
Server tries to find type of oneof member in the request protobuf message.
Server rejects requests since it can't determine the type of oneof message.

Can you give an example of the source .proto file, the relevant section of the generated .pb.go file, and the protoc command you are running? Thanks.


Live Events in GCCH

Live Events are currently available in GCCH but must be set up via a powershell command. Can you please update this page to indicate it is also available in GCCH but needs to be set up via powershell https://docs.microsoft.com/en-us/microsoftteams/teams-live-events/set-teams-live-events-policies-using-powershell#allow-users-to-schedule-live-events

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

ID: 2b679199-caa5-4cc5-27e5-60a2cf999f69
Version Independent ID: 6878c954-e248-94c2-7602-47437ec7a2dd
Content: Plan for live events in Microsoft Teams - Microsoft Teams
Content Source: Teams/teams-live-events/plan-for-teams-live-events.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


<EMAIL_ADDRESS>decompress error

Extracting FurMark_<IP_ADDRESS>_Setup.exe ... ERROR Exit code was 1!
Failed to extract files from C:\Soft\Scoop\apps\furmark\<IP_ADDRESS>\FurMark_<IP_ADDRESS>_Setup.exe.
Log file:
C:\Soft\Scoop\apps\furmark\<IP_ADDRESS>\innounp.log
The setup files are corrupted or made by incompatible version. Maybe it's not an Inno Setup installation at all.
(00492DAA)

Duplicate of #11476


Logout not working for Keycloak <10

Summary
In Keycloak versions below 10, there is no /realms/{realm-name}/protocol/openid-connect/revoke endpoint and the server side logout must be done to /protocol/openid-connect/logout endpoint with refresh token in "refresh_token" parameter. However gatekeeper sends this parameter with name "token".
Environment

OS: Debian
Go (e.g. go version)
Server (e.g. Keycloak or any other IdP): Keycloak 9.0.13
Gatekeeper: 1.3.3-rc1

Expected Results
/oauth/logout should invalidate token
Actual Results
Keycloak responds with bad request and gatekeeper fails to logout the user with error in the logs
error	invalid response from revocation endpoint	{"status": 400, "response": "{\"error\":\"invalid_request\",\"error_description\":\"No refresh token\"}"}

Steps to reproduce
Use Gatekeeper 1.3.3-rc1 with Keycloak version 9. Perform logout via /oauth/logout

@OskarsPakers there is EnableLogoutRedirect parameter this would not work for you?

@p53 missed that one. In fact, it works for me. I`ll just redirect users to keycloak logout url.
I think it is not worth implementing a workaround for the revocation endpoint then.


something broken with v4.5.0 regarding scale_factor / zoom level ?

I've upgraded node-mapnik on my kosmtik install to v4.5.0 and the scale_factor or zoom in cartocss seems completely broken, rendering all zoom levels like the highest one.
Downgrading to v4.4.0 solve the issue immediately.
I'm running on node v12 (current LTS)

@cquest - thanks for reporting.

@cquest - I found the issue: default scale_denominator value should be initialised to 0.0 in order to trigger
 if (scale_denom <= 0.0)
 {
     scale_denom = mapnik::scale_denominator(m_req.scale(), map_proj.is_geographic());
 }

could you try a1a08d0 and see if everything is working as expected? cheers

I've installed node-mapnik with (not sure about it, I'm not used to this):
npm i mapnik/node-mapnik#a1a08d077fff7474f05fe04fd7f1af4eb49c3c07
Re-ran kosmtik... and still the same problem
npm i<EMAIL_ADDRESS>-> ok again

@cquest ok, I don't thinks you can just pull new binary package like that, thanks for trying!  I'm pretty sure this issue is fixed in a1a08d0 but I found couple more issues I'll need to fix before publishing 4.5.1

I'll check 4.5.1 once it's available.
Thanks for your lightning fast feedback !

The v4.5.1 release is available now and should fix this. Please re-open if you find it did not and please create new issues for other other problems you encounter. Thanks @cquest!

I've just tested with 4.5.1 (npm i<EMAIL_ADDRESS>and the problem is still there...
reverted with npm i<EMAIL_ADDRESS>and all is ok.
It does not seem fixed.

@cquest - ok, must be something else here. Could you provide more info e.g carto css, anything else relevant to replicate this issue, please.

@artemp I see that there is still one scale_denom defaulting to 1. Perhaps that is the problem?
$ grep 'double scale_denominator =' src -r
src/mapnik_vector_tile_composite.cpp:    double scale_denominator = 0.0;
src/mapnik_vector_tile_composite.cpp:    double scale_denominator = 0.0;
src/mapnik_map_render.cpp:        double scale_denominator = 1.0;
src/mapnik_map_render.cpp:    double scale_denominator = 0.0;
src/mapnik_map_render.cpp:    double scale_denominator = 0.0;
src/mapnik_map_render.cpp:    double scale_denominator = 0.0;
src/mapnik_vector_tile_render.cpp:    double scale_denominator = 0.0;

@springmeyer that could be it, indeed.

We're having a similar issue. maximumExtent https://github.com/mapnik/node-mapnik/blob/master/src/mapnik_map.cpp#L235-L250 seems to only expect floats, no longer strings.
But even if we convert them beforehand we still see similar issues.

@ticktricktrack maximumExtent (settter) now expect JS array of exactly four floating point numbers. I don't think accepting and converting strings internally to floats is a good design.
@ticktricktrack @cquest - I just published<EMAIL_ADDRESS>Let me know, cheers

It seems ok with v4.5.2 :)

ok, great, closing, thanks.


Roll back if rollover::overwrite fails when appending events to the DB

Previously we were allowing the following scenario:

RolloverCompleted event is appended to the events table.
RolloverCompleted event data fails to be appended to rollover_completed_event_data for whatever reason.

That scenario would leave us in a situation where the state between the two tables would be inconsistent.
To fix it, we ensure that the rollback logic doesn't just cover rollover::overwrite::overwrite, but rather the entirety of append_event.
Fixes https://github.com/itchysats/itchysats/issues/2662.

@holzeis: I'm gonna start using https://www.conventionalcommits.org/en/v1.0.0/ in this repo at least.
The only downside I see is that I get less space to write the commit title, but otherwise I really like the idea.

bors r+
I've fixed the build and opted for using the SqliteConnection type instead of Acquire, which leads to even less code. I'm merging to speed things up, but I'm asking for reviews to raise awareness about this change. In practice I think it's just the same but easier.
The Acquire docs already kind of recommend this approach, but I missed this: https://docs.rs/sqlx/latest/sqlx/trait.Acquire.html.