Example subscribe error

Hi.
I'm testing your library, but I couldn't compile the example of subscribe:
import Sblendid from "@sblendid/sblendid";

const batteryServiceUuid = "180f";
const batteryLevelUuid = "2a19";
(async () => {
  const peripheral = await Sblendid.connect(peripheral =>
    peripheral.hasService(batteryServiceUuid)
  );
  const batteryService = await peripheral.getService(batteryServiceUuid);
  await batteryService.on(batteryLevelUuid, batteryLevel => {
    console.log("Battery Level", batteryLevel.readUInt8(0), "%");
  });
})();

Compile error:
TSError: ⨯ Unable to compile TypeScript:
src/testConn.ts:60:29 - error TS2345: Argument of type '"2a19"' is not assignable to parameter of type "never".
     await batteryService.on(batteryLevelUuid, batteryLevel => {
                               ~~~~~~~~~~~~~~~~
src/testConn.ts:60:47 - error TS7006: Parameter "batteryLevel" implicitly has an "any" type.

     await batteryService.on(batteryLevelUuid, batteryLevel => {

Can you help me?
Thanks a lot

Hey there,
I'm sorry, the examples are in a pretty bad state, I am not at version 1.0.0 with this library so things are still a bit messy. Try this code:
import Sblendid from "@sblendid/sblendid";

const batteryServiceUuid = "180f";
const batteryLevelUuid = "2a19";
(async () => {
  try {
    console.log("Searching for a peripheral");
    const peripheral = await Sblendid.connect(peripheral => {
      process.stdout.write(".");
      return peripheral.hasService(batteryServiceUuid);
    });
    console.log("Found", peripheral);
    const batteryService = await peripheral.getService<any>(batteryServiceUuid);
    await batteryService!.on(batteryLevelUuid, (batteryLevel: any) => {
      console.log("Battery Level", batteryLevel.readUInt8(0), "%");
    });
  } catch (error) {
    console.log(error);
    process.exit(1);
  }
})();

What I did is to use any (which noone should) and ! to tell TypeScript that the service is definitely not there, which it cannot be sure of.
If you are on TypeScript you need to have
{
  "compilerOptions": {
    "target": "ES2015"
  }
}

in your tsconfig.json
and you need to install
npm i @types/node --save-dev

for this to work.
But I am very afraid this example still fails. This will fix TypeScript but you will receive the error

Error: Failed to turn on notifications for 2a19

which is probably my bad. This example is not right yet. Unfortunately I want to implement Linux support first before I can fix this issue. I am somewhat sure that the problem lies in trying to subscribe to this specific service uuid, which probably can't be done this way (so the example is bad) and not that the library is broken because I know of other users who work with subscriptions.
You can try reading the battery level instead of subscribing to it:
import Sblendid from "@sblendid/sblendid";
const batteryServiceUuid = "180f";
const batteryLevelUuid = "2a19";
(async () => {
try {
console.log("Searching for a peripheral");
const peripheral = await Sblendid.connect(peripheral => {
process.stdout.write(".");
return peripheral.hasService(batteryServiceUuid);
});
console.log("Found", peripheral);
const batteryService = await peripheral.getService(batteryServiceUuid);
const batteryLevel = (await batteryService!.read(
  batteryLevelUuid
)) as Buffer;

console.log("Battery Level", batteryLevel.readUInt8(0), "%");

} catch (error) {
console.log(error);
process.exit(1);
}
})();

Thanks. Linux support is very important for me. I have already solved this problem by list the characteristics and using the on('event',...) method. Your library is the best I found. But it is very difficult to find, which is a pity. Sorry for my english.
Thanks for the great work!!!

Oh thank you so much. I will still keep this in mind, of course I want this to be bug-free for version 1.0.0. Btw your English is totally fine!


🇸🇦 Be prepared for the new Google Cloud region Dammam (Kingdom of Saudi Arabia)

Source: https://twitter.com/uhoelzle/status/1557089770345414656
» https://en.wikipedia.org/wiki/Dammam

me-central2 ?

Added to gcp.yml and pricing.yml is calculated. Missing in test.sh!

https://github.com/Cyclenerd/google-cloud-pricing-cost-calculator/issues/95


About SpeakTextAsync, I only want the audioData, Don't want a sound, How to config ?

Here is the JAVA code:
try {
      SpeechSynthesisResult result = synthesizer.SpeakTextAsync(text).get();
      if (result.getReason() == ResultReason.SynthesizingAudioCompleted) {
          synthesizer.StopSpeakingAsync();
          System.out.println("Speech synthesized for text [" + text + "]");
          audioData = result.getAudioData();
      } else if (result.getReason() == ResultReason.Canceled) {
          SpeechSynthesisCancellationDetails cancellation = SpeechSynthesisCancellationDetails.fromResult(result);
          System.out.println("CANCELED: Reason=" + cancellation.getReason());

          if (cancellation.getReason() == CancellationReason.Error) {
              System.out.println("CANCELED: ErrorCode=" + cancellation.getErrorCode());
              System.out.println("CANCELED: ErrorDetails=" + cancellation.getErrorDetails());
              System.out.println("CANCELED: Did you update the subscription info?");
          }
      }

      result.close();
  } catch (Exception e) {
      e.printStackTrace();
  } finally {
      synthesizer.close();
}

You can take a look at the following code. It has samples that show how to save the audio to a wav file, an mp3 file or a push/pull audio stream. You can use one of these instead of playing the audio through the speakers. https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/java/jre/console/src/com/microsoft/cognitiveservices/speech/samples/console/SpeechSynthesisSamples.java

Oh, thank you~ I solved the problem.


Update to use HFC for all protocol modes

We decided that it is simpler to have things be more uniform and use the
HFC for all protocol modes, and so in particular for the Byron-only and
Shelley-only modes.

bors merge

bors r+


Language server does not terminate

The problem seems to be that the destructor of QueueManager, the last shared_ptr for one of the waiters is destroyed. This causes the destruction of the MultiQueueWaiter, which contains a std::condition_variable_any, which contains a pthread_cond_t. pthread_cond_destroy doesn't work well (it hangs) if there are active pthread_cond_waits on the same condition variable.
In general the termination logic seems hard to understand and is probably wrong.

Thanks.
I think the most robust solution here is to just not destroy QueueManager on shutdown. The OS should handle cleaning up the pthread state for us.


need help to decrypt a lua file

A friend has encrypt my file on my server and hes now away and he dont want give me the shit password i need a decrypter or anything like that please

Actually, I could decrypt it. There is a piece of backdoor in my code. I could get the decrypted content.
If it's OK for you to let me examine the decrypted content legal or not. You can paste the file under this issue and tell some detail about the content.

dcheroica5.zip
por favor ayúdame a descifrar este script. quiero editarlo, por eso necesito descifrarlo
el men que lo actualizaba se fue de Youtube :"

dcheroica5.zip
@Jean132309

The password is a 14 bytes length IP address.
The original code just like this.
-------------------------------------------------------------------------
gg.alert('⚫DRAGON CITY HACK⚫\n❗Save Menu❗ 🐞Fixed Bugs🐛\n☑working☑ ⭐Star 5 Fixed⭐ New\n☑Goals☑ new\n🔵2021/8/4🔵\nℹv5.9.3 Updateℹ\n☑Script Fixed New☑\n')
-------------------------------------------------------------------------
TG =
gg.makeRequest("https://sociok.com/*********************************").content
if not TG then
else
pcall(load(TG))
end

Notice, It's a simple XOR encrypt. Telling you the original code, you could get the password by simple XOR original code and encrypted bytes.
I won't tell you the password directly.


Fix click to zoom at disable clustering zoom level

With disableClusteringAtZoom on and spiderfyOnMaxZoom off, this would simply do nothing when clicking on a cluster at the zoom level before clustering is disabled.
Now with spiderfyOnMaxZoom not disabled, it will only spiderfy at the map's max zoom rather than the zoom level configured for disableClusteringAtZoom (the cluster's max zoom). Is this the expected behaviour?
Note: we're having this issue with the v1.0.0-beta.2.0 version, it seems it wasn't an issue in v0.4.0

Is this related to #633 ?
The value of _maxZoom should be map.getMaxZoom, unless it is changing at some stage?
https://github.com/Leaflet/Leaflet.markercluster/blob/master/src/MarkerClusterGroup.js#L879-L893
Could you log it to see if it is changing, a repro would be good thanks.

Hi,
Actually _maxZoom is purposely modified right at line 891 to match the zoom level before the specified disableClusteringAtZoom option when the latter is used.
Going back to using this._map.getMaxZoom() instead of this._maxZoom would be the exact reversal of PR #609…
So @matt-in-a-hat you are saying that you leave spiderfyOnMaxZoom at true, use disableClusteringAtZoom at some lower level than map's max zoom, and see no spiderfication when clicking on a cluster at disableClusteringAtZoom - 1? That would probably be against the expected behaviour indeed.

Repro https://jsfiddle.net/yez9wn01/3/
@ghybs it is the same issue as #633
Doing what you said about merging line 802 and 804 seems to fix the issue https://jsfiddle.net/yez9wn01/4/

Updated repro (previous seemed to have ssl issue loading leaflet): https://jsfiddle.net/yez9wn01/5/
And repro with fix mentioned above: https://jsfiddle.net/yez9wn01/6/

Hi,
For clarity, here is your version 6 modified using directly leaflet.markercluster-src.js from tag 1.0.0-beta.2.0 through https://rawgit.com/ service:
https://jsfiddle.net/yez9wn01/7/
The modified _zoomOrSpiderfy method is then included in the JS section of the JSFiddle.
This modification (i.e. merging if conditions from current lines 802 and 804) would probably be a better move than using back this._map.getMaxZoom() (which would reverse PR #609).
Could be worth adding a dedicated test case as well?
Hope this helps.

Fixed by #657


[tf] logrotate on host log file size

Motivation
This is to solve the devnet disk usage issue.

We should be rotating the log on the host, change the path to the host log.
daily has higher priority on logrotate config, but daily file size is way too big. Let's rotate only based on the file size

Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
Apply on my workspace

@bors-libra delegate+

:v: @sherry-x can now approve this pull request

@sausagee we generate 100M too quickly, like in 10 mins or so. I will test out different config later, maybe we should just set log level to debug

@bors-libra r=sausagee

:pushpin: Commit bafbc4d has been approved by sausagee

:hourglass: Testing commit bafbc4d1a315615259545c8419b3edfb5dea3106 with merge b2ee9a5f0ccc7e6585dfdc0250dd2105c10f56ef...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: sausagee
Pushing b2ee9a5f0ccc7e6585dfdc0250dd2105c10f56ef to master...


How to hide a message from a custom User

Suppose two users join to the webchat: User1 and Agent.
I want to hide the messages of Agent, but keep sending the message he wrote to the bot.
What I'm trying to do is a hand off to an Agent.
So the Agent will join to the conversation with the id Agent.
I'm able to recognize when the agent and the user are talking. When User1 and Agent are on the same conversation, I "stop" the bot and use it to send the messages of the Agent through him.
The problem is that I don't know how to hide in the webchat the input text of the Agent so the user doesn't see a duplicate message (the input of the agent and the output of the bot).
I need to change the webchat HTML, but don't know how to hide the text of the Agent.

You can intercept certain activities and prevent them from being passed to Web Chat by adding a middleware store. In the middleware, you can check for certain conditions and can choose to render the activity by calling and returning the result of the next method or ignoring it by returning null. Take a look at the code snippet below.
const store = createStore(
  {},
  ({ dispatch}) => next => action => {
    if (action.type === 'DIRECT_LINE/INCOMING_ACTIVITY') {
      if ( // IGNORE CONDITIONAL ) {
        return
      }
    }
    return next(action)
  }
);

renderWebChat({
  directLine,
  store,
}, document.getElementById('webchat'));

In the future, the Microsoft Bot Framework team prefers that how to questions like this one to be submitted on Stack Overflow. The official Bot Framework Github repos are the preferred platform for  submitting bug fixes and feature requests.


Customm object detection implementation

Hey
I have been trying models for custom object detection, and after training a model with 500 examples and 8 epochs.
The training run smoothly and everything goes well, however, when I try to evaluate this model, I get the following output:
===============================
Model File:  data/0500_run_00/models/detection_model-ex-008--loss-  14.427.h5

Using IoU :  0.5
Using Object Threshold :  0.3
Using Non-Maximum Suppression :  0.5
deadpool: 0.0000
mAP: 0.0000

This happens to every single model I try to evaluate.
However, when I use the same model to get predicions over some of the evaluation images, I get lots of bounding boxes which does not looks that bad, so mAP=0.0000 doesn't looks  accordingly.
I think it may be related to those mismatches between current and original implementation as pointed out in #352 and #338
What I will try is to download the original implementation and compear it against the current to see what other differences I found, and document those here, to try to understannd why are those differences there and if them explain this strange behaviour, but would like to hear your thougths on this @OlafenwaMoses meybe I'm missing some other thing

I found that init.CustomObjectDetection.detectObjectsFromImage operation uses init.CustomDetectionUtils.correct_yolo_boxes line 1270 but the init.DetectionModelTrainer.evaluateModel calls the utils.evaluate operation here  which also calls the correct_yolo_boxes from the util module: those both implementations on current ImageAI version are different, but they are exactly the same in the original implementation, as seen in #352
Up to this point, my guess is that maybe, the implementation on init.CustomDetectionUtils.correct_yolo_boxes was sligthly modified to use square images, assuming/forcing them to be square before calling it, but it was not adjusted in the evaluate method.
This may explain why those methods differ, I still have different results while detecting than when testing, and this leaves #352 as correct (maybe strange but ok)

Well it turn out that the initial issue that lead me to open this issue was that I didn't provide the validation folder properly, so the actual evaluation folder was empty. This make me think that the number of validation samples (and maybe the training ones) must be printed. What's more: the library should warn the user when no training/validation files are found.
I'll try to add this to the generator.
That said, the difference I found while reading the code is still unexplained:

I found that init.CustomObjectDetection.detectObjectsFromImage operation uses init.CustomDetectionUtils.correct_yolo_boxes line 1270 but the init.DetectionModelTrainer.evaluateModel calls the utils.evaluate operation here which also calls the correct_yolo_boxes from the util module: those both implementations on current ImageAI version are different, but they are exactly the same in the original implementation, as seen in #352

I'll close this issue and move the yet usefull information to #352 which is far more related


there is no such thing as an MIT/X11 license

From
http://en.wikipedia.org/wiki/MIT_License
When you write MIT/X11 or MIT/X, you refer to a different license than the one
called "MIT".

+1
package.json mentions MIT, but the license text mentions MIT/X11. Such license probably doesn't even exist and moreover, it means the package is provided under a very non-standard license, i.e. legally it is unusable in most projects.


Add v4 NonfungiblePositionManager skeleton

Description of changes
This PR adds the base skeleton for NonfungiblePositionManagerV4
So this is mostly copied from v3-periphery but I made a few changes:

Pool IDs are now just PoolKeys (instead of having a separate counter => address mapping)
I removed references to WETH9 specifically (until we decide on what to do about WETH in v4)
Added LiquidityManagement to manage lock/lock callback logic
Added createAndInitializePoolIfNecessary directly to the contract and func args take in PoolKey instead of ids
Added tokenByIndex, tokenOfOwnerByIndex, and totalSupply - think these were added to ERC721Enumerable?

TODO (next steps):

[ ] fill in function definitions (everywhere that says // TODO: implement this)
[ ] add tests
[ ] Use permit2 version of ERC721Permit?

Closing in favor of https://github.com/Uniswap/v4-periphery/pull/141


[ELWMM] Mud Magic - After character creation game crashes when entering world

Module Information

Identifier: ELWMM
Module Name: Mud Magic
Version: 1.22

Describe the bug
After character creation game crashes when entering world
To Reproduce
Steps to reproduce the behavior:

Add module to moduleConfig.json
Load MBBSEmu
Enter Mud Magic module
Create Character
See error

Expected behavior
Enter and play game
Screenshots
Unhandled exception. System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'Unknown Exported Function Ordinal in MAJORBBS: 162')
   at MBBSEmu.HostProcess.ExportedModules.Majorbbs.Invoke(UInt16 ordinal, Boolean offsetsOnly)
   at MBBSEmu.HostProcess.ExecutionUnits.ExecutionUnit.ExternalFunctionDelegate(UInt16 ordinal, UInt16 functionOrdinal)
   at MBBSEmu.HostProcess.ExecutionUnits.ExecutionUnit.Execute(IntPtr16 entryPoint, UInt16 channelNumber, Boolean simulateCallFar, Boolean bypassState, Queue`1 initialStackValues, UInt16 initialStackPointer)
   at MBBSEmu.Module.MbbsModule.Execute(IntPtr16 entryPoint, UInt16 channelNumber, Boolean simulateCallFar, Boolean bypassSetState, Queue`1 initialStackValues, UInt16 initialStackPointer)
   at MBBSEmu.HostProcess.MbbsHost.WorkerThread()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.ThreadHelper.ThreadStart()

Software Information:

OS: Windows 2019 Server Standard
Telnet Client: NetRunner

This is delbtv - delete current btrieve record


Resource dnacenter_wireless_profile does not support adding new SSIDs to profile

Prerequisites

[x] Have you tested the operation in the API directly?
[x] Do you have the latest Terraform provider version?
[x] Review the compatibility matrix before opening an issue.

Describe the bug
It seems like the dynamic block on the profile_details section of the module, is both sorting and using a list index when the SSIDs are tied to the profile. This makes so, adding a new SSID, triggers a change on all previous SSIDs as the index has changed.
Adding a new "Test" profile triggers:
# dnacenter_wireless_profile.this["Wireless_devhf"] will be updated in-place
  ~ resource "dnacenter_wireless_profile" "this" {
        id   = "name:=Wireless_devhf"
        # (1 unchanged attribute hidden)

      ~ parameters {
          ~ profile_details {
                name  = "Wireless_devhf"
                # (1 unchanged attribute hidden)

              ~ ssid_details {
                  ~ name          = Voice" -> Test"
                    # (1 unchanged attribute hidden)

                    # (1 unchanged block hidden)
                }
              ~ ssid_details {
                  ~ name          = Wireless" -> Voice"
                    # (1 unchanged attribute hidden)

                    # (1 unchanged block hidden)
                }
              ~ ssid_details {
                  ~ name          = "eduroam" -> Wireless"
                    # (1 unchanged attribute hidden)

                    # (1 unchanged block hidden)
                }
              + ssid_details {
                  + enable_fabric = "true"
                  + name          = "eduroam"

                  + flex_connect {
                      + enable_flex_connect = "false"
                    }
                }

                # (2 unchanged blocks hidden)
            }
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

In adition, applying this change (and living with the consequences of changing everything on the profile) crashes the resource/provider:
Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

dnacenter_wireless_profile.this["Wireless_devhf"]: Modifying... [id=name:=Wireless_devhf]
╷
│ Error: Plugin did not respond
│
│   with dnacenter_wireless_profile.this["Wireless_devhf"],
│   on wireless.tf line 106, in resource "dnacenter_wireless_profile" "this":
│  106: resource "dnacenter_wireless_profile" "this" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may contain more details.
╵

Stack trace from the terraform-provider-dnacenter_v1.1.22-beta plugin:

panic: reflect: call of reflect.Value.Type on zero Value

goroutine 29 [running]:
reflect.Value.Type({0x0?, 0x0?, 0xc000bde000?})
        reflect/value.go:2453 +0x12e
github.com/go-resty/resty/v2.typeOf({0x1307b20?, 0x0?})
       github.com/go-resty/resty/v2@v2.7.0/util.go:247 +0xaa
github.com/go-resty/resty/v2.kindOf({0x1307b20?, 0x0?})
        github.com/go-resty/resty/v2@v2.7.0/util.go:259 +0x25
github.com/go-resty/resty/v2.handleRequestBody(0xc000db8000, 0xc0007a0680)
        github.com/go-resty/resty/v2@v2.7.0/middleware.go:441 +0x7b
github.com/go-resty/resty/v2.parseRequestBody(0xc000db8000, 0xc0007a0680)
        github.com/go-resty/resty/v2@v2.7.0/middleware.go:150 +0x153
github.com/go-resty/resty/v2.(*Client).execute(0xc000db8000, 0xc0007a0680)
        github.com/go-resty/resty/v2@v2.7.0/client.go:909 +0x1a9
github.com/go-resty/resty/v2.(*Request).Execute.func1()
        github.com/go-resty/resty/v2@v2.7.0/request.go:769 +0x89
github.com/go-resty/resty/v2.Backoff(0xc00088ca98, {0xc00088ca70, 0x5, 0xc00000e9e8?})
        github.com/go-resty/resty/v2@v2.7.0/retry.go:105 +0x19b
github.com/go-resty/resty/v2.(*Request).Execute(0xc0007a0680, {0x1554ab8?, 0x15568bc?}, {0x1582413, 0x23})
        github.com/go-resty/resty/v2@v2.7.0/request.go:763 +0x537
github.com/go-resty/resty/v2.(*Request).Put(...)
        github.com/go-resty/resty/v2@v2.7.0/request.go:704
github.com/cisco-en-programmability/dnacenter-go-sdk/v5/sdk.(*WirelessService).UpdateWirelessProfile(0x1813648?, 0x0)
        github.com/cisco-en-programmability/dnacenter-go-sdk/v5@v5.0.13/sdk/wireless.go:1451 +0x3d0
terraform-provider-dnacenter/dnacenter.resourceWirelessProfileUpdate({0x1813648, 0xc000e0e360}, 0x0?, {0x1424f80?, 0xc0000c6160})
        terraform-provider-dnacenter/dnacenter/resource_wireless_profile.go:424 +0x40d
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).update(0xc00036d260, {0x1813680, 0xc000ea41b0}, 0xd?, {0x1424f80, 0xc0000c6160})
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.27.0/helper/schema/resource.go:767 +0x12e
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0xc00036d260, {0x1813680, 0xc000ea41b0}, 0xc00054b380, 0xc00106c900, {0x1424f80, 0xc0000c6160})
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.27.0/helper/schema/resource.go:874 +0x83a
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0xc000118030, {0x1813680?, 0xc000ea4060?}, 0xc000deba90)
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.27.0/helper/schema/grpc_provider.go:1024 +0xe3c
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0xc00023c000, {0x1813680?, 0xc000e9d7a0?}, 0xc000df98f0)
        github.com/hashicorp/terraform-plugin-go@v0.18.0/tfprotov5/tf5server/server.go:821 +0x574
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0x14f9d20?, 0xc00023c000}, {0x1813680, 0xc000e9d7a0}, 0xc000df9880, 0x0)
        github.com/hashicorp/terraform-plugin-go@v0.18.0/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:422 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc00038a000, {0x18163a0, 0xc0006c51e0}, 0xc000e5be60, 0xc0009da930, 0x1efb520, 0x0)
        google.golang.org/grpc@v1.57.0/server.go:1360 +0xe13
google.golang.org/grpc.(*Server).handleStream(0xc00038a000, {0x18163a0, 0xc0006c51e0}, 0xc000e5be60, 0x0)
        google.golang.org/grpc@v1.57.0/server.go:1737 +0xa1b
google.golang.org/grpc.(*Server).serveStreams.func1.1()
        google.golang.org/grpc@v1.57.0/server.go:982 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
        google.golang.org/grpc@v1.57.0/server.go:980 +0x18c

Error: The terraform-provider-dnacenter_v1.1.22-beta plugin crashed!

Expected behavior
Adding a new SSID into the for_each loop should not trigger a change on the whole resource, only adding the new SSID via the dynamic block. The map elements should not be sorted before being pushed into the state, and indexes should never be used unless the variable is a set that does not change.
Screenshots
Please provide an screenshot of the successful API call with cuRL, Postman, etc.
Environment (please complete the following information):

Cisco DNA Center version and patch: <IP_ADDRESS> - 70852
Terraform version: 1.5.6
Cisco DNA Center provider version: 1.1.22-beta
OS Version: Ubuntu

Additional context
Add any other context about the problem here.

Hi @edudppaz , do you don't have more logs about this?

@edudppaz do you test new version?

@edudppaz do you test new version?

Hi @fmunozmiranda
The provider does not crash anymore, but still wants to change the ssids tied to the profile on each apply, and now it also removes the assigned sites to the profile, as commented in my other issue

This is fixed, follow up in #233


Add missing bracket at the end of package.json file

npm install was failling due to missing bracket

Merged as https://github.com/thoughtbot/neat/commit/f68fdbd586d38492273173cf3f7be2d2a7ac468f. Thanks!


Add GHC 8 builds

GHC 8 warnings are fairly useful.
/jury approved @charleso

👍

Can't figure out what's pulling in that dependency, don't have time to figure it out, will just cherry-pick these warning-fix commits.


[BUG] Failed to establish a new connection: [Errno 61] Connection refused when trying to import

What is the bug?
Cannot import the library. I got this error
ConnectionError: ConnectionError(<urllib3.connection.HTTPSConnection object at 0x144b90940>: Failed to establish a new connection: [Errno 61] Connection refused) caused by: NewConnectionError(<urllib3.connection.HTTPSConnection object at 0x144b90940>: Failed to establish a new connection: [Errno 61] Connection refused)
What is your host/environment?

OS: MacOS 13,0,1
Version 1.0.0b1

Okay after I dig into the code, I think the version is still not updated with this commit f353dfaa038f1c153b1ca1966477dcbb72eb98dd, so this line is still in the opensearch_py_ml/common.py after I installed the library
OPENSEARCH_HOST = "https://instance:9200"
OPENSEARCH_ADMIN_USER, OPENSEARCH_ADMIN_PASSWORD = "admin", "admin"

# Define client to use in tests
OPENSEARCH_TEST_CLIENT = OpenSearch(
    hosts=[OPENSEARCH_HOST],
    http_auth=(OPENSEARCH_ADMIN_USER, OPENSEARCH_ADMIN_PASSWORD),
    verify_certs=False,
)
# in github integration test, host url is: https://instance:9200
# in development, usually host url is: https://localhost:9200
#it's hard to remember changing the host url. So applied a try catch so that we don't have to keep change this config
try:
    OS_VERSION = os_version(OPENSEARCH_TEST_CLIENT)
except opensearchpy.exceptions.ConnectionError:
    OPENSEARCH_HOST = "https://localhost:9200"
    # Define client to use in tests
    OPENSEARCH_TEST_CLIENT = OpenSearch(
        hosts=[OPENSEARCH_HOST],
        http_auth=(OPENSEARCH_ADMIN_USER, OPENSEARCH_ADMIN_PASSWORD),
        verify_certs=False,
    )
    OS_VERSION = os_version(OPENSEARCH_TEST_CLIENT)

Hi, the beta version expects to have a opensearch connection already which we are going to change in our next GA version(this will be releasing soon).

Hi, mfarrelm, 1.0.0 is released. Can you please upgrade the version?
I'm closing the issue for now. Please feel free to open if version upgrade doesn't work for you. Thanks.


Various fixes

Summary of the pull request

Dev Home (Canary) will now auto install GitHub Extension (Canary) instead of Preview.
Dev Home (Dev) will not install anything.
Building PluginSDK will no longer force Dev Home to build as release.

References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist

[ ] Closes #1239
[ ] Closes #1240
[ ] Tests added/passed
[ ] Documentation updated

Please give the PR a better name before merging.


1.16 - GrassColor2 & FoliageColor2

After discussing in discord it seems this has not carried over to 1.16 because it would require the mod client side.
A possible solution could be to re-add it but have it so that the client mod is needed to be able to see it, and if not installed then things look as they do right now.
There are hundreds of biomes in Wildlands that make use of this feature so it would be super disappointing to not be able to carry that work over properly from 1.12.

Screenshot of what it does:

Colors be back with 0.0.15, courtesy of Josh!


Caching reference resolver

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@089daeb). Click here to learn what that means.
The diff coverage is 16.66%.

@@            Coverage Diff            @@
##             master      #11   +/-   ##
=========================================
  Coverage          ?   38.09%
=========================================
  Files             ?        8
  Lines             ?      210
  Branches          ?       21
=========================================
  Hits              ?       80
  Misses            ?      127
  Partials          ?        3

Impacted Files
Coverage Δ

pubsub/validators/resolver.py
0% <0%> (ø)

pubsub/validators/validator.py
79.41% <83.33%> (ø)

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 089daeb...c8d547a. Read the comment docs.


cmp-nvim doesn't work outside of .config/nvim directory

I'm not getting any code completion or error messaging in any files that are outside the .config/nvim directory.
Everything else seems to be working normally like map keymaps, theme etc. This is using the init.lua as it is without alteration.
https://user-images.githubusercontent.com/34646768/210508466-1503b78d-530c-45c9-88d0-194934290146.mp4
I'm on MacOS.

I just ran this: rm -rf ~/.local/share/nvim/ and reinstalled neovim, and Mason LSP things etc.. got it working.


Please support TFLite gradient operations: BroadcastGradientArgs, StridedSliceGrad and some other

Within our company we trained a breakthrough realtime model which requires automatic differentiation feature at runtime. To be more specific, the model's output should be forward pass outputs + derivative of runtime loss function with respect to some input control variables.
We use TFLite to run the model, but we can't use TF Select kernels because our runtime environment is very strict (video gaming consoles). In the current state, when we try to use tf.gradients within our model the TFLite converter does not convert because of some operations to be not supported: BroadcastGradientArgs, DynamicStitch, EluGrad, Sign, StridedSliceGrad, UnsortedSegmentSum
As a workaround, we approximate the derivatives with finite difference method, but obviously it requires to make extra forward passes + it introduces some numerical instability to the model. It would be very helpful to have cheap analytical derivatives with a backpropagation step within TFLite.
System information

Linux rb15 5.12.14-arch1-1 #1 SMP PREEMPT Thu, 01 Jul 2021 07:26:06 +0000 x86_64 GNU/Linux
TensorFlow 2.5.0 from tensorflow-opt-cuda package (https://archlinux.org/packages/community/x86_64/tensorflow-opt-cuda)

Provide the text output from tflite_convert
Some ops are not supported by the native TFLite runtime, you can enable TF kernels fallback using TF Select. See instructions: https://www.tensorflow.org/lite/guide/ops_select
TF Select ops: BroadcastGradientArgs, DynamicStitch, EluGrad, Sign, StridedSliceGrad, UnsortedSegmentSum
Details:
	tf.BroadcastGradientArgs {device = ""}
	tf.DynamicStitch {device = ""}
	tf.EluGrad {device = ""}
	tf.Sign {device = ""}
	tf.StridedSliceGrad {begin_mask = 0 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 0 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 0 : i64}
	tf.StridedSliceGrad {begin_mask = 0 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 0 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 1 : i64}
	tf.StridedSliceGrad {begin_mask = 0 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 1 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 0 : i64}
	tf.StridedSliceGrad {begin_mask = 0 : i64, device = "", ellipsis_mask = 1 : i64, end_mask = 0 : i64, new_axis_mask = 2 : i64, shrink_axis_mask = 0 : i64}
	tf.StridedSliceGrad {begin_mask = 1 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 0 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 0 : i64}
	tf.StridedSliceGrad {begin_mask = 1 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 1 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 0 : i64}
	tf.StridedSliceGrad {begin_mask = 1 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 1 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 2 : i64}
	tf.StridedSliceGrad {begin_mask = 1 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 1 : i64, new_axis_mask = 2 : i64, shrink_axis_mask = 0 : i64}
	tf.StridedSliceGrad {begin_mask = 3 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 3 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 0 : i64}
	tf.StridedSliceGrad {begin_mask = 3 : i64, device = "", ellipsis_mask = 0 : i64, end_mask = 3 : i64, new_axis_mask = 0 : i64, shrink_axis_mask = 4 : i64}
	tf.UnsortedSegmentSum {device = ""}

It will take time to review and add ops. You can use https://www.tensorflow.org/lite/guide/ops_select at the moment to unblock the conversion.

@thaink is there any thread or doc where we can see which ops are under review for the upcoming tensorflow releases? It will help us immensely to plan our internal projects that need to run in really constrained tflite runtime environments and cannot use select ops. Thanks!

The requests are tracked in https://github.com/tensorflow/tensorflow/issues/21526

Hi @barabanus, it seems like the ops are now supported according to  https://github.com/tensorflow/tensorflow/issues/21526, please close as completed if there are no other open items regarding this. Thanks.

Thanks, @pkgoogle


editing the list of OpenShift versions

For the latest controller version 1.6.x, the list of versions of OpenShift Origin and OpenShift Container Platform was incorrect. v3.6 and v3.8 were not tested.

@amudukutore this PR only removes the two versions from the matrix that you mentioned were not tested. can you review?


Make optional use of Geo-Location

It could be useful to take a users Geo-Location into account for either logging in, or for firing triggers. After all it wouldn't always make sense to open the front door if the user isn't actually in front of the door.
This probably should be rather configured per trigger (and included in the JSON payload), and possibly even dependent on who the users is. The reasoning for this is, that trusted users may have to be able to fire a trigger regardless of where they are, while for others a specific physical location is required. Of course this will not help if the location is spoofed. But as an additional layer of protection this could be useful.

Oneliner to get location data in JS:
navigator.geolocation.getCurrentPosition(function(position){console.log(position)})


Integrated console inconsistent behavior with regular PS console - Copy-Item

VSCode Version: 1.26.1
OS Version: Win10

Steps to Reproduce:

Open VScode -> Powershell Integrated Console

from any folder try to execute command like Copy-Item ".\Default_files" "$($env:APPDATA)\Microsoft\Signatures\Something_Default_Files" -Recurse -Force
(Result will be all files in .\Default_files\ will be copied to ...\Something_Default_Files\ - into that directory (no subdirs created)) assuming there is a subfolder called Default_files.

Now open regular PS console, navigate to the same folder as step 2) and execute the same command - the result will be a subdirectory \Default_Files\ under "$($env:APPDATA)\Microsoft\Signatures\Something_Default_Files"

why there is different behavior between the two? You can try adding a * wildcard to create ".\Default_Files*" which will then work in the normal console copying files only, but it won't copy anything at all in VSCode console and not return any error.

Does this issue occur when all extensions are disabled?: Yes/No
Yes. Checked in the insiders without any extensions as well - looks the same.
Thank you!

https://github.com/PowerShell/vscode-powershell


Redis DB crash after reboot\shutdown on VMWARE

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I am convinced that mine is new.

Describe the bug
Every time i'm shutting down the ESXi or just the VM itself, the Redis DB used for NtopNG doesn't stop clean, so I need to reset on each reboot
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Expected behavior
Describe alternatives you considered
Screenshots
If applicable, add screenshots to help explain your problem.
95978:C 29 Mar 2021 10:28:51.398 # Redis version=5.0.9, bits=64, commit=00000000, modified=0, pid=95978, just started
95978:C 29 Mar 2021 10:28:51.398 # Configuration loaded
29986:M 29 Mar 2021 10:28:51.399 # Server initialized
29986:M 29 Mar 2021 10:28:51.399 # Short read or OOM loading DB. Unrecoverable error, aborting now.
29986:M 29 Mar 2021 10:28:51.399 # Internal error in RDB reading function at rdb.c:2124 -> Unexpected EOF reading RDB file
If applicable, information from log files supporting your claim.
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant, e.g.:
Running on VMWare
OPNsense 21.1.3_3-amd64
FreeBSD 12.1-RELEASE-p14-HBSD
OpenSSL 1.1.1j 16 Feb 2021

Disk corruption, nothing we can do here.

Disk corruption, nothing we can do here.

ok.. but I think there is a problem..
I'm shutting down the VM from the CLI, so the disk should be powered off clean

How I can recreate the flowd database?

Reporting: Settings: Reset NetFlow data
I wouldn't trust the hypervisor unconditionally. We have seen issues with Hyper-V that after update and reboot the old version was still there...

Reporting: Settings: Reset NetFlow data
I wouldn't trust the hypervisor unconditionally. We have seen issues with Hyper-V that after update and reboot the old version was still there...

Cannot speak for Hyper-V, but I'm sure that a clean shutdown on VMWare doesn't distrupt filesystem.
I've other two VMs on my ESXi node (Linux) and the filesystem is clean on each shutdown/reboot

The fact that it did indeed disrupt the file system is irrelevant to the narrative I guess. As I said: there is nothing anyone can do and this is not the upstream project to take disk corruption bug reports.


Prioritize certain operations over others

Is your feature request related to a problem? Please describe.
While indexing 10K records we delete a document, that delete operation will now be in queue until all the 10K records are indexed. we should probably be able to specify the priority of these operations or at least allow to perform certain operations immediately instead of queueing them up.
Describe the solution you'd like
Allow to specify the priority of indexing operations, for example DocumentDelete will be performed right away before indexing documents
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
it creates a large delay to remove a document which in some cases is important than indexing other documents.

Hello @VinceG! Thanks for your report!
I don't think this is in our current roadmap. However, we have a public roadmap where our user can share their ideas and their needs. It would be awesome if you can add your idea so that other users will upvote it if they need it as well.
https://roadmap.meilisearch.com/tabs/5-ideas

@curquiza Thank You! Submitted.


General re-factor of TestClass for cleanup after recent changes.

Code has become a little bit bloated and messy while adding memory leak detection and fixtures, so needs some general maintenance.

Completed primary clean-up although some future re-factoring is still planned.


Upgrade Dotty 0.22.0-RC1

Upgrade to use version 0.22.0-RC1 release of Dotty (released today!).
No changes was required (all tests green), but there are two new features introduced in 0.22 that I opted in on.

Grouping of extension methods (less code and cohesion)
Use using instead of previous given for implicits context parameters

I think the new syntax for context parameters is a good change, but might cause confusion with our use of using following a test context. At a conceptual level they are, somehow, both correct (both deal with using a context) - but a change on our side might still be needed? If so, any thoughts on new name?
Details at https://dotty.epfl.ch/blog/2020/02/05/22nd-dotty-milestone-release.html

as?
class StatefulTest extends TestSuite with State[Cart] with
  "an empty cart" as Cart() to :
    "with two items" as (_.add(CartItem("beach-chair", 2))) to :
      "and another three items" as (_.add(CartItem("sunscreen", 3))) to :
        "contains 5 items" in :
          cart => expect(cart.totalQuantity).toEqual(5)

But it's a bit confusing with as, to and in. Not easy to remember when to use what...

No not easy, and not with Dotty being a moving target =)
Anyhow, I think that we should revisit the terms used, see what can be simplified in both names and order, but in a separate PR / thread.


Misleading error for deprecated stack versions in Functions

Describe the bug
The error message provided when attempting to create a function app is inaccurate and misleading. It should be updated to provide a true statement.
Related command
az functionapp create
Errors

dotnet-isolated has reached EOL on 2024-11-12 and is no longer supported. https://azure.microsoft.com/en-us/updates/dotnet6support/

Issue script & Debug output
az group create -n $groupName -l $location -o none
az storage account create --sku Standard_LRS -l $location -g $groupName -n $storageName --kind StorageV2 -o none
az functionapp create -g $groupName -n $appName -s $storageName --consumption-plan-location $location --functions-version 4 --runtime dotnet-isolated --runtime-version 6

Expected behavior
The issue is that the above message implies that support has ended for the stack ("dotnet-isolated") and not the specific version of the stack (here, .NET 6). Newer versions like .NET 9 are of course perfectly fine to pick at the time of this issue being opened.
Instead, the CLI should specify that the given version has reached end of support. The support state should also be spelled out (not using an acronym) and use active voice. There should also be a call to action. I would expect something more like:

Support ended for version "6" of stack "dotnet-isolated" on 2024-11-12. Please use a supported version instead. For additional information, see https://azure.microsoft.com/en-us/updates/dotnet6support/.

Environment Summary
azure-cli                         2.67.0
core                              2.67.0
telemetry                          1.1.0
Extensions:
resource-graph                     2.1.0
Dependencies:
msal                              1.31.0
azure-mgmt-resource               23.1.1
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\mahender.azure\cliextensions'
Python (Windows) 3.12.7 (tags/v3.12.7:0b05ead, Oct  1 2024, 02:44:45) [MSC v.1941 32 bit (Intel)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
It stands out to me that the link provided in the error message is for the Web Apps end-of-support announcement. It's valid to point at that, but it makes me think that the behavior here is at least partially being driven by the App Service commands. The link itself does not show up in the Stacks API, and I haven't looked to see if it is somehow constructed in the CLI, but I suspect that's where it comes from.

Thank you for opening this issue, we will look into it.


testing, dont mind

Obviously this was not intended to merge against upstream, I am sorry for the noise, Closing!


Update Helm release ingress-nginx to v3.23.0

This PR contains the following updates:

Package
Update
Change

ingress-nginx
minor
3.21.0 -> 3.23.0

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (3.23.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Security hygiene for keypairs/private keys

We have a number of hygiene tasks to take care of with regards to private keys:

[ ] remove Display and Debug impls for KeyPair / private key so it isn't easy to print them out
[ ] genesis tool must not read private keys from commandline arguments
[ ] validator can read private key from separate (non config) file
[ ] final audit of configs to make sure there are no keypairs/private keys in them

This may duplicate some other issues - i did a quick search and couldn't find anything

/cc @kchalkias @joyqvq @punwai since the pattern of implementation of keys in the system is moving really fast
(see also https://github.com/MystenLabs/narwhal/issues/537 https://github.com/MystenLabs/sui/pull/2994 https://github.com/MystenLabs/sui/pull/3191 )

related: #1478 which would indicate the last item is done.


Console (UI): Expert mode

With the release version 2.0, we introduced a Console (UI) that provides an easy way to deploy clusters using a graphical interface. Now we are planning to add Expert Mode to unlock advanced user interface options tailored for experienced users.
This mode reveals additional settings and features that allow for precise configuration of clusters, including complex parameter adjustments not visible in the standard mode, including:

[!NOTE]
Expert mode is disabled by default to provide a simple mode to simplify the user experience and can be enabled (if necessary) on the Settings page.

1. Custom server type
The ability to specify another server (instance) type that is not represented in the console list (for cloud deployments).
2. Spot instances
The ability to select Spot instances when creating a cluster (for cloud deployments).

3. Volume and File System Type
The ability to select volume and file system type when creating a cluster (for cloud deployments).

4. Network
The ability to specify a Network/VPC (for cloud deployments).

If provided, the server will be added to this network (needs to be created beforehand).

5. DCS
The ability to select the type of DCS (etcd or consul), deploy new servers, or use an already deployed DCS cluster.

6. Data directory
The ability to redefine the data directory path.

7. Databases
The ability to add databases and users when creating a cluster.

8. Connection pools
The ability to configure PgBouncer connection pooler when creating a cluster.

9. Extensions
The ability to choosing extensions when creating a cluster.

10. Backups
The ability to configure Backups when creating a cluster.

11. Postgres and system settings
The ability to configure Postgres and system (kernel) settings when creating a cluster.

12. Additional settings
The ability to choosing additional settings when creating a cluster.

13. YAML tab
Another function for "Expert Mode" could be to provide a "YAML tab" where all current parameters are displayed in the form of variables. This tab would also allow users to set predefined values for functions that may not have been added to the UI yet but are available through automation capabilities.

Note: Access to the Figma project with all implementation details will be provided during development.

Consider sponsoring the project via GitHub or Patreon

If you're interested in this feature, please consider becoming a sponsor.
The development of this feature requires sponsorship to fund developer efforts. If you're already a sponsor and are interested in this feature, please leave a comment here so we can prioritize this issue accordingly.
We also welcome contributions from those willing to dedicate their time to implement this feature on a voluntary basis. Please see the Contributing Guide for more information.

Also consider the possibility of managing public access, setting variables:
ssh_public_access: true  # Allow public ssh access (required for deployment from the public network).
ssh_public_allowed_ips: ""  # (comma-separated list of IP addresses in CIDR format) If empty, then public access is allowed for any IP address.
netdata_public_access: true  # Allow access to the Netdata monitoring from the public network (if 'netdata_install' is 'true').
netdata_public_allowed_ips: ""  # (comma-separated list of IP addresses in CIDR format) If empty, then public access is allowed for any IP address.
database_public_access: false  # Allow access to the database from the public network.
database_public_allowed_ips: ""  # (comma-separated list of IP addresses in CIDR format) If empty, then public access is allowed for any IP address.


Why LiDAR shift is needed in evaluation for visualizing?

Thanks for your great work. I'd like to ask that why the evaluation and visualization needs shift from LiDAR? Is it from the relative depth estimation of Dust3R? Or the LiDAR is actually not needed in evaluation (the model is by itself scale and shift aware)?

I want to save a visual point cloud so that it matches the lidar point cloud well. I tried to use align_and_vis.py but the point cloud of each frame doesn't look like a lidar point cloud.
I see that shift_z compensation is needed in the eval.py, as well as the operation of ICP registration GT and PRED to match GT as much as possible, is this because Dust3r estimates the inaccurate pose? I would like to ask you for some guidance.

Thank you for your attention. In the evaluation, the predicted point cloud has not yet been transformed to the scale of world coordinate system, thus we need the scale and shift to align GT and predicted point, but in visualization they are not used.
Besides, I can not get the point that "the point cloud of each frame doesn't look like a lidar point cloud". Do you mean that the LiDAR points are sparse while predicted points are dense? Please elaborate.

I get the point. I hope the following explanation can address your concern.
(1) Driv3R is DUSt3R-based, so the inference result can not reflect the scale and shift of real world, and we need to use the align script to transform all points to world coordinate system.
(2) If you want to apply visualization on more generalizable cases, I recommend to use the average median GT depth as the arg.scale, the value 120 is solely our calculation that fits for NuScenes.
If you have any problem, feel free to let me know.

I'd like to summarize my understanding. If I want to save a 4d image point that is very similar to the corresponding lidar point clouds as described in table.2. I need to follow the procedure of eval.py and transform the predicted point cloud to the lidar point scale. Please check if I am right. Thanks again for your help!

One correction. To get the result in Table 2, you do not have to transform the predicted points to the scale of LiDAR points, you only need to do so for visualization in the real world coordinate system. For depth evaluation, just transform the predicted and GT points to a uniform coordinate system.

I find that the predicted points is transformed to LiDAR scale in Regr3D_t_ScaleInv.get_all_pts3d_t() in eval.py. I mean the evaluation on points but not depth.
I am confused why the predicted coordinate system is not uniform with the GT points (the ICP process in eval.py). Is it related to the pose estimation process in Dust3R?
I'm a new comer of 3D geometry.

The predicted points are in the first frame's coordinate system originally, but they do not reflect the scale of real world (please see DUSt3R paper for details). To evaluate, you need to transform both predicted and GT points to a uniform coordinate system (that is what we do before line 207 in eval.py). To visualize in the world coordinate system, you need to transform the predicted points to align the real world scale (that is what we do before line 162 in align_and_vis.py).

Thanks for your answering! I will take a closer look at the related papers and codes.


[Experimental] PPX + dynamic forms support

This PR implements PPX that introduces input/output concept. It handles the most basic use-case (see example), for now. But might be extended to support all features of current non-ppx implementation + dynamic forms.
Config shape:
module Form = [%form
  type input;
  type output;
];

input holds data that are shown in UI. Usually, these are strings or bools.
output is what you get in submit handler if form is fully valid.
Both input and output types must be records with the same set of fields (definitions must be inlined). In the simplest possible case, when input is the same as output, the latter can be alias of the former:
module EmailForm = [%form
  type input = {email: string};
  type output = input;
];

Validators are defined as an argument of useForm hook which gets generated by ppx. A type signature of validators is changed: instead of list of validators it's a record, with same fields as input/output types. Validator function must return value of field type in output record (instead of Valid | NoValue variant) wrapped in result. Basically, it's guaranteed on type level that you'd be able to submit a form only when all validators returned Ok(outputValue).
Use cases:

input/output are the same

module EmailForm = [%form
  type input = {email: string};
  type output = input;
];

let validators: EmailForm.validators = {
  email:
    Some({
      strategy: OnFirstSuccessOrFirstBlur,
      validate: ({email}) => {
        switch (email) {
        | "" => Error("Email is required")
        | _ as value when !Email.regex->Js.Re.test_(value) =>
          Error("Email is invalid")
        | _ => Ok(email)
        };
      },
    }),
};

<EMAIL_ADDRESS>let make = () => {
  let form =
    LoginForm.useForm(
      ~validators,
      ~initialInput={email: ""},
      ~onSubmit=(output, form) => { ... },
    );

  <Form className="form" onSubmit={form.submit}>

      "Email"->React.string

    <input
      id="email-field"
      type_="text"
      value={form.input.email}
      disabled={form.submitting}
      onBlur={_ => form.blurEmail()}
      onChange={event =>
        form.updateEmail({
          ...form.input,
          email: event->ReactEvent.Form.target##value,
        })
      }
    />
    {switch (form.emailResult()) {
     | Some(Error(message)) =>

         message->React.string

     | Some(Ok(_)) =>

         {j|✓|j}->React.string

     | None => React.null
     }}
    <button disabled={form.submitting}>
      (form.submitting ? "Submitting..." : "Submit")->React.string
    </button>
  </Form>;
};

input/output are different

module EmailForm = [%form
  type input = {email: string};
  type output = {email: Email.t};
];

let validators: EmailForm.validators = {
  // Since `input.email` & `output.email` of different types
  // there must be a validator that would produce value of `output` type
  // so validator is required, hence it's not of `option` type
  email: {
    strategy: OnFirstSuccessOrFirstBlur,
    validate: ({email}) => {
      // Email.parse: string => result(Email.t, Email.error)
      switch (email->Email.parse) {
      | Error(NoValue) => Error("Email is required")
      | Error(InvalidValue) => Error("Email is invalid")
      | Ok(email) => Ok(email)
      };
    },
  },
};

// Component code is the same as in previous example

custom message & submissionError types

// Defaults:
// type message = string;
// type submissionError = unit;
module EmailForm = [%form
  type input = {email: string};
  type output = {email: Email.t};
  type message = I18n.t;
  type submissionError = BadEmail | UserExists;
];

Collections, dependent fields & async forms are not implemented yet so examples below are just drafts that might be changed.

collections

module BlogPostForm = [%form
  type input = {
    title: string,
    authors<EMAIL_ADDRESS>array(author)
  }
  and author = {name: string};
  type output = input;
];

let validators: BlogPostForm.validators = {
  title: Some({ ... }),
  authors: {
    collection:
      Some(({authors}) => {
        switch (authors->Array.length) {
        | 0 => Error("At least one author is required")
        | _ => Ok()
        };
      }),
    fields: {
      name:
        Some({
          strategy: OnFirstSuccessOrFirstBlur,
          validator: ({authors}, ~at as index) => {
            switch (authors->Array.getUnsafe(index)) {
            | {name: ""} => Error("Author name is required")
            | {name} => Ok(name)
            };
          },
        }),
    }
  },
};

let form = BlogPostForm.useForm(...);

form.addAuthor({name: ""});
form.removeAuthor(~at=index);
form.updateAuthorName(~at=index, {name: ""});
form.authorNameResult(~at=index);

dependent fields

module MyForm = [%form
  type input = {
    password<EMAIL_ADDRESS>passwordConfirmation] string,
    passwordConfirmation: string,
    title: string,
    fieldWithMultipleDeps<EMAIL_ADDRESS>(field, author.name)] string,
    authors<EMAIL_ADDRESS>array(author),
  }
  and author = {name: string};
  type output = input;
];

async form

// Either using separate extension point
module MyAsyncForm = [%form.async
  type input = {email: string};
  type output = input;
];

// Or field level attribute
module MyAsyncForm = [%form
  type input = {email<EMAIL_ADDRESS>string};
  type output = input;
];

The main downside of this approach I see is that more code gets generated. It can be optimized in some ways but still. Also, source code became more complex.
Why field type is gone?
Initially, I prototyped ppx output using field type + GADTs but in the end I bumped into type issue when I can't preserve type information while passing action(i, o) type to React.useReducer. I could manage this part to compile only by hiding GADT types with existential wrapper but it wouldn't work since this information is required b/c validators return result('output, 'message) type which is field specific (output bit).
The code below results in the following error:
This definition has type
  state * ('a action -> unit)
which is less general than
  'a0. state * ('a0 action -> unit)

type field(_) =
  | Title: field(string)
  | Published: field(bool);

type state = {
  title: string,
  published: bool,
};

type action('a) =
  | Change(field('a));

type interface = {
  updateTitle: unit => unit,
  updatePublished: unit => unit,
};

let initialState = {title: "", published: false};

let useForm = () => {
  let reducer: type a. (state, action(a)) => state =
    (state, action) =>
      switch (action) {
      | Change(field) => initialState
      };
  let x: type a. (state, action(a) => unit) =
    reducer->React.useReducer(initialState);
  let (state, dispatch) = x;

  {
    updateTitle: () => dispatch(Change(Title->Field)),
    updatePublic: () => dispatch(Change(Public->Field)),
  };
};

If it's possible to solve this case, it would probably help to reduce amount of generated code. On the other hand, I'm not sure that code size difference would make a huge difference and dumb set of functions is easier to manage (e.g. debugging/error messages).

Anyway, appreciate feedback on this experiment.
/cc @baransu @mlms13

This looks great IMO! We're big on domain driven design and reformality is one of the things we use to be a gatekeeper for our data.
The way we use our forms is the same as the way you have written it out above. At the input level everything is a string, bool and we try to parse the data onto the types that we're expecting.
One of the things that might be improved is the update<fieldName> function. If that didn't need to take in the previous input state then you would reduce the complexity of the update since you could clobber over a previously updated value if you are sending in a stale input state.
I love what you're doing and if there's anything you can section out and need/want some help on LMK.

I really like new validations syntax, one record instead of a list is in most cases better.
As @johnhaley81 pointed - it would be great to treat update<fieldName> function as setState where it receives state => state function instead of state.
What collections does @form.collection is ppx intended to support? Is it only an array or other types like list or Belt.Map.String could be possible?
Types have to be inlined in [%form]. This is harder if you're type is more complex and you're wrapping it into a module to hide implementation details.
I'm using the forked version on reformality (mostly described here: https://github.com/MinimaHQ/re-formality/issues/43#issuecomment-482797082). My use-case is hardcore - it's used to handle complex graph with few levels of nesting. For most of the cases, proposed ppx is a great solution but it would be great to opt-out of it and create more complex cases by hand.

@johnhaley81 @baransu Thanks for feedback!

One of the things that might be improved is the update function. If that didn't need to take in the previous input state then you would reduce the complexity of the update since you could clobber over a previously updated value if you are sending in a stale input state.
As @johnhaley81 pointed - it would be great to treat update function as setState where it receives state => state function instead of state.

It makes perfect sense! Will change this 👍

What collections does @form.collection is ppx intended to support? Is it only an array or other types like list or Belt.Map.String could be possible?

The rules here are the same as for non-collection fields except it must be array of records. I need type information for each field in collection the same way as for the root fields to keep track of the state of each field in collection. I use type name inside an array for looking up the record type definition inside a list of items in the config module.

Types have to be inlined in [%form]. This is harder if you're type is more complex and you're wrapping it into a module to hide implementation details.

Yeah, this is unfortunate requirement that I can't overcome yet since I need names of the fields and type information. With ppx, I can get this only when these things are inlined.

I'm using the forked version on reformality (mostly described here: #43 (comment)). My use-case is hardcore - it's used to handle complex graph with few levels of nesting. For most of the cases, proposed ppx is a great solution but it would be great to opt-out of it and create more complex cases by hand.

It's totally possible since ppx generates c/p'able code. In this scenario, it acts more like scaffolder of the base implementation that can be updated by hand.

if there's anything you can section out and need/want some help on LMK

That's a bit hard in the current state since I'm doing changes all over the place while reimplementing existing functionality. I'll definitely ping you once there will be pieces that can be implemented in parallel!

<EMAIL_ADDRESS>is in.

AFAICT all features of non-ppx version are implemented.
Changes since the first post:

validators definition is moved to config. It allowed a number of optimizations + it's possible to unwrap validators, e.g. if validator exists just define it. If it doesn't, set it to None.

let validators = {
  email: {
    strategy: OnSubmit,
    validate: ...,
  },
  remember: None,
};

Async mode can be turned on on per field basis (instead of affecting a whole form).

[%form
  type input = {
    email<EMAIL_ADDRESS>string,
    password<EMAIL_ADDRESS>{mode: OnBlur}] string,
  };
];

Signature of async validator gets changed: it accepts output type of the value that is returned from sync validator, this way it's guaranteed on a type level that async validator wouldn't be called unless sync validator returned Ok(x). I want to get feedback on this (e.g. would anyone need input record or single value should be enough (I assume it should but)).

validateAsync: 'outputValue => Js.Promise.t(result('outputValue, 'message))

Result of async field is:

type asyncResult('outputValue, 'message) =
  | Validating('outputValue)
  | Result(result('outputValue, 'message));

switch (form.emailResult()) {
| Some(Validating(_)) => <Spinner />
| Some(Result(Ok(_))) => ...
| Some(Result(Error(error))) => error->React.string
| None => React.null
}

With<EMAIL_ADDRESS>implemented, I think things are pretty much ready for the first beta.
I also added skeletons of 2 types of test suits:

ppx tests: for now these tests check error messages produced by ppx
integration tests

Not much of tests are actually written though.
I imagine the plan would be:

Clean up few warnings in generated code.
Update examples.
Update docs.
Configure CI.
Release first beta.
Add critical tests.
If all ok, stable release.

--
@johnhaley81 @baransu I updated signature of updateField() functions so those take input => input argument but spotted very unfortunate issue. This code would produce runtime error:
<input
  value={form.input.name}
  onBlur={_ => form.blurName()}
  onChange={event => {
    form.updateName(_input => {name: event->ReactEvent.Form.target##value});
  }}
/>

It happens due to synthetic events pooling. Since callback gets triggered asynchronously, by the time it gets called, event is already null'ed. To fix this, it should be written this way:
<input
  value={form.input.name}
  onBlur={_ => form.blurName()}
  onChange={event => {
    let value = event->ReactEvent.Form.target##value;
    form.updateName(_input => {name: value});
  }}
/>

Which seems very subtile. What are your thoughts on this?

@johnhaley81 Pinging you on RC.
I'm almost finished with the docs (rest few will be finished tomorrow): https://github.com/MinimaHQ/re-formality/tree/ppx/docs
And published RC: re-formality@next

Thanks @alexfedoseev I'm going to pull it down now and test it out!

@alexfedoseev would it be possible at all to have different fields in input and output?
For example say we want to make a date/time picker with fields:
type input = {
  minutes: int,
  hours: int,
  day: int,
  month: int,
  year: int
};

We'd really want an output of a Js.Date.t and not all of these fields.
type output = Js.Date.t;

Would that be a possible change?

@johnhaley81 Yeah, for now it's not possible to combine multiple fields into single type. But I thought about<EMAIL_ADDRESS>(or something like this) which suppose to handle this kind of thing. Though I didn't look into details of it yet.

Would it be possible to also supply lenses as well for the fields?
Something like:
type input = {
  password: string,
  email: string
};

let getPassword: input => string;
let setPassword: (string, input) => input;

let getEmail: input => string;
let setEmail: (string, input) => input;

I keep thinking of things as I'm going through it to only get to the solution later in the docs 😂😂
I'll save my comments then till the end and then I'll do a write up.

Really quick prototype of<EMAIL_ADDRESS>type input = {date<EMAIL_ADDRESS>date'}
and date' = {
  minutes: int,
  hours: int,
  day: int,
  month: int,
  year: int,
};

type output = {date: Js.Date.t};

type validators = {
  date: {
    entity: date' => result(Js.Date.t, message),
    fields: {
      minutes: {
        strategy: Strategy.t,
        validate: input => result(int, message),
      },
      ...
    }
  }
};

// Interface
form.updateDateMinutes(1)
form.dateMinutesResult
form.dateResult

@alexfedoseev I'm getting a type error while trying to define submissionError.

@johnhaley81 Will take a look soon.

@johnhaley81 Published 4.0.0-beta.2 with the fix.

@alexfedoseev the submissionError fix works great!
A lot of the forms are cleaner now and much easier to understand what's going on. This is a great change!
One of the things that I was thinking about was with with the setters (i.e. update<fieldName>)
With the runtime exception issue, maybe it's better to have the function that passes in the state to be a different one? So the default setter could be update<fieldName> which just takes in the value and blindly plops it into the state and a more advanced one update<fieldName>WithState would give you copy of the latest state if you needed it.
I also liked that entity change. Would it need that<EMAIL_ADDRESS>tag or would the ppx be able to derive it since the field is a record?

I also liked that entity change. Would it need that<EMAIL_ADDRESS>tag or would the ppx be able to derive it since the field is a record?

It would require attribute b/c in AST it would be just Ptyp_constr and it would require parsing of the whole structure for each field to find out if it's record or not. So it's easier and faster to be explicit here.
I will create separate issue to discuss details since I have one more use-case for record field in mind and I'm not sure yet if it would be useful and if it would how to split 2 these attributes.

With the runtime exception issue, maybe it's better to have the function that passes in the state to be a different one? So the default setter could be update which just takes in the value and blindly plops it into the state and a more advanced one updateWithState would give you copy of the latest state if you needed it.

Also tend to move it to separate issue. In general, the less api the better and both of ways have own caveats, so instead of one issue it would probably give us two and more things to keep in mind for users.

I extracted all leftovers to own issues. Looks like ready to merge!

Merging. I think it makes sense to keep it on @next tag for sometime and add some integration tests. Then publish as latest.


Test native segment_csr behavior, add documentation for integralTransform to website

Adds tests for segment_csr, cleans up docstrings, updates the trees for autogenerated Sphinx docs website, changes the forward call signature for a GINO to take x instead of f for maximum compatibility.

Looks like there's a typo that's breaking the tests.

Looks good, thanks David!


Add Case sensitivity to editor.action.addSelectionToNextFindMatch

We use this feature a lot in our daily development activities however since it is case-insensitive, it tends to select items that are unintended. A perfect example is defining an instance of a class and wishing to rename the instance references but not the class itself:
var user = new User(); <-- cmd+d would select 'user' & 'User' when only the instance variable is intended
user.firstName = 'Joe';
user.lastName = 'Smith';

@jayrosen1576 The find widget toggles also control the behaviour of cmd+d. The toggles can be used even when the find widget is hidden:
Here are the mac keybindings:

case sensitive: cmd+alt+c
whole words: cmd+alt+w

While this does seem to work it is a bit clunky and not well known as an option. I would assume cmd+d would function case-insensitive as most other text editors do with maybe cmd+alt+d as a case-sensitive selection.


fix(naming): rename "plugin" into "webhook"

This affects all artifacts including the repository itself, which is renamed after the merge of this PR

"plugin" still occurs in the image because its derived from the repo name, so this will be temporary phenomena


MC: takeoff throttle ramp should not start when disarmed

Any idea how this broke?

It didn't break, it got implemented that way. This is only a problem if you switch to mission before you arm.

Will implement this asap, quick work

Fixed on master


Memory allocation for large values

Right now, some basic profiling has revealed that Particle Swarm Optimization, and maybe the package in general, has some large allocations in memory.
This is expected to some degree, but it will be useful to consider the following in the future:

Check type stability.
Use tools like ProfileView.jl and Coverage.jl to analyse memory allocation and possible bottlenecks.

It really doesn't matter as long as the evaluation time is reasonable, which it is. In the case of type stability this is also true for the package as of build #32 .
In the meantime, I will close this issue but most likely will add benchmarks using BenchmarkTools in a special directory or something.


Invalid rpush definition.

This change is inconsistent with other signatures documented with @method tags as we decided to use array in case of variadic commands such as RPUSH.


⚠ Secret Website 3 has degraded performance

In 3c3cdc4, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 1952 ms

Resolved: Secret Website 3 performance has improved in dfc0fe1.


chore, refactor, feat(egen): Follows new template, markdown fixes, refactors

This PR includes the following updates to the `notebooks/official/pipelines/rapid_prototyping_bqml_automl.ipynb` notebook:

budget_milli_node_hours are specified to reduce the training time.
removes IS_TESTING condition in the cleanup step.
replaces REGION with LOCATION.
replaces dsl.Condition (is deprecated) with dsl.If.
addd a clean up step for the locally generated pipeline package file.
adds link for Colab enterprise.
removes future tense (will).
contracts words (do not, you are etc.).
image links are no longer accessible and hence are removed
fixes typos (aboyt, election).
removes the usage of "we".

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

/gcbrun

/gcbrun


[WIP] Improve Share Button UI/UX

Description
This PR improves the UI of the share button to also show the domain name:

Also TODO:

[ ] Improve error handling with a timeout? (freezes at fetch stage)
[ ] Fix tests (warning due to regex)

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

Pull Request Test Coverage Report for Build 5718

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 34.353%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/controlBar/ControlBarShareButton.tsx
0
6
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/commons/controlBar/ControlBarShareButton.tsx
1
0%

Totals

Change from base Build 5676:
-0.05%

Covered Lines:
1713

Relevant Lines:
4616

💛  - Coveralls


Add a favicon to the website

Since there is no favicon currently we can put one there.
This issue is opened under Hacktoberfest 2022.
I would like to work on this issue.

Actually, i would like to do that personally myself
It is not there for a reason.
I feel that adding just a favicon is not a good contribution to the repo.
But, if you have any suggestions about the favicon please add them in comments.
And if you want to make any significant changes to the webapp, you can open an issue and contribute.
Thanks


Sec 1.2: Update text and code examples

In European languages, numbers are usually represented using a string of the ten digits 0, 1, 2, 3, 4, 5, 6, 7, 8 and 9.

This is more or less universal, save for things like legal documents in some countries.  i.e. everyone is taught the Arabic numerals.  Indeed, as the same suggests, this numbering system was developed outside of Europe.
The section uses measurements in a less than elegant way.  Namely things like:
for j in range(n):
    qc_output.measure(j,j)

can be replaced by:
qc_output.measure(range(n), range(n))

Note that this result comes from a quantum simulator, which is a standard computer calculating what a quantum computer would do.

What an ideal quantum computer would do.

Simulations are only possible for small numbers of qubits, but they are nevertheless a very useful tool when designing your first quantum circuits.

Small is a relative concept. Best to give a rough idea of the number here.

If this convention seems odd to you, don’t worry. It seems odd to lots of other people too, and some prefer to number their bits the other way around.

This reads: "Qiskit does it in a weird way, and everyone thinks so".  It is very much done so so that numbers are expressed naturally in the bit strings, and things like QFT follow their definitions.

Traditionally, in the study of digital computation, this is called an XOR gate.

For people who are not familiar with digital logic gates, a truth table specifying the operation of these gates would be nice.

There are multiple ways to explain the effect of the CNOT. One is to say that it looks at its two input bits to see whether they are the same or different. Then it writes over the target qubit with the answer. The target becomes 0 if they are the same, and 1 if they are different.

Another way of explaining the CNOT is to say that it does a NOT on the target if the control is 1, and does nothing otherwise. This explanation is just as valid as the previous one (in fact, it’s the one that gives the gate its name).

Again a truth table would go a long way here.

This also needs work:

The main difference is that they use qubits, a variant of the bit that can be manipulated in quantum ways


docs: add carbon svelte implementation

Closes #
This PR introduces Svelte as a language/framework that implements Carbon. It is akin to Angular and Vue in that it is community supported.
Changelog
New

add Svelte as a new implementation

Changed

{{change thing}}

Removed

{{removed thing}}

@dakahn Good catch – added.


Age is displayed incorrectly in now ls

While executing now ls I noticed that the age of a deployment I just made was displayed wrong.
I guess that the time gap between deploying and executing now ls was too small, therefore the age value was too small for the cli to handle it.

@leo is this a platform bug or CLI bug?


Anchors setting when training on the custom dataset

Hey, I find your code is clean and elegant. When training on my dataset, I have two questions about anchors:

What is the relationship between these float anchors and interger anchors in comment?
1.25 is 12 scaled by 8 times?  1.875 is 36 scales by 16 times?

MODEL = {"ANCHORS":[[(1.25, 1.625), (2.0, 3.75), (4.125, 2.875)], # Anchors for small obj(12,16),(19,36),(40,28)
[(1.875, 3.8125), (3.875, 2.8125), (3.6875, 7.4375)], # Anchors for medium obj(36,75),(76,55),(72,146)
[(3.625, 2.8125), (4.875, 6.1875), (11.65625, 10.1875)]], # Anchors for big obj(142,110),(192,243),(459,401)
"STRIDES":[8, 16, 32],
"ANCHORS_PER_SCLAE":3
}

Is that necessary to use kmeans algorithm to generate new anchors when training on the custom dataset?

Looking forward to your reply.

你好，请问你跑自己的数据集能够跑通吗


refactor: add pacote to resolve template name instead of arborist workaround

Description

add pacote dependency
cleanup arbortis mock and add new one for pacote
modify generator.js as suggested

Related issue(s) fixes: #1102

@derberg @akkshitgupta Can you try deprecating the version of pacote to 15.1.1 in the package.js? I tried it in my copied branch of my forked repository, and it seems to pass the ubuntu test after I deprecated it.

Link to my PR

let's maybe wait for https://github.com/asyncapi/generator/pull/1069 that will release new generator major release dropping support for older nodes where pacote may have issues?

@akkshitgupta please solve merge conflicts

Hello @derberg, after resolving conflicts, I am getting this error while running test. Can you have a look at here

@akkshitgupta you can update your PR. There is a conflict with package-lock. Just solve it locally by running npm install with verbose flag, of course after first merging latest upstream to your branch, the installation will update package-lock

@akkshitgupta please have a look into failing tests

Hey @derberg, its working now. It was an issue on the server side. on the previous update, there some network issue.test failed  because of improper dependency installation.

@akkshitgupta still failing

Apologies for the delay @derberg. I couldn't pay much attention due to some problems. I looked into it, but couldn't find the reason. i guess, it is failing because of the template version and I don't know how tk solve it.

Hey @akkshitgupta please resolve the conflicts, just change the file structure

Hey @akkshitgupta your test are failing, please resolve it and feel free to ask for any help if yu need

@akkshitgupta you need to solve conflicts

@akkshitgupta tests are failing for some strange reasons. Please consult chatgpt that gives some hints that you need to try out. Basically something related to mock and jest config

@akkshitgupta do you plan to continue with this one?

Apologies @derberg
Being occupied, I wasn't able to pay much attention to the issue for a while now, unfortunately.
someone else can take it up.


Side by side diff for arbitrary commits

I found it somewhat strange that though we could view side by side diff for uncommitted files, it could not be done for files from some previous commit. So I propose to introduce an explore button in the toolbar of commit diff view :

Which takes the user to the side by side diff for the files in that commit:

Thanks an lot for your contribution.
I just fixed some minor ergonomic glitches and reworked the FileListView to make it handle properly long paths
Anyway, thanks for your work, I'm really happy to see people contributing :)

Thank you for merging this.
I have been looking for a web based alternative to magit for some time and found this to be a simple and convenient solution.
Also thanks for taking care of the UI glitches.


Warning Viro...Manager requires main queue setup since it overrides 'constantsToExport'

I'm getting a whole lot of warnings: Viro...Manager requires main queue setup since it overrides 'constantsToExport' since I upgraded viro into my existing project:
"react": "16.3.1",
"react-native": "^0.55.3",
"react-viro": "2.6.0",

Testing both versions of react-native 0.55.1 and 0.55.3 on the hello world viro sample, they both seem to work fine.  What is causing this warning on my project?  Should I suppress the warnings or somehow fix the warnings instead?

Hi @mypark,
That's an interesting warning you have there. We don't see this warning on new or updated projects on our side, however, it could be visible due to a build setting on your existing project that isn't set on new React Native projects.
The platform should still work with the warnings, so you can either suppress it for now, or live with them. I believe the fix for the warnings needs to occur on our side, so I've created an issue on our side and we'll try to address it in our next release.
Thanks for letting us know!

This was also reported by someone in our Slack, in order to diagnose this issue further, I have a few questions:
What Xcode version are you using?
Did you upgrade from 2.5.0?
Do you also see this on a new project? (react-viro init NewProj)
Thanks,

Hi @mypark,
Thanks for the update, are you still seeing it on your upgraded project?
We think we fixed the warnings for our next release, but have been unable to reproduce it.
Due to it not reproducing on a new project, it does possibly point to some npm package conflict. Maybe compare your package.json files between your existing project and the one you just react-viro init'd.

I'm trying to re-create a vanilla project and upgrade it to get you the warning but having some troubles getting a new project upgraded.  I'll see if I can post a sample project later with the reproducible warnings.

@mypark I am having this issue, I figured out it was because I am using react-navigation. Removing this package completely gets rid of these warnings.
I still haven't figured out how to use react-navigation within a react-viro project without these warnings..


Aliexpress blocking

Have you tested how many listings you can scrape before Aliexpress attempts to block you?

It depends, I think. Sometimes you need a lot of proxies for massive scraping.

I'm the developer behind Aliseeks.com , we offer an API which can help you get product details. I recommend you take a look at our API Documentation.

I'll have a look soon.


License service stores enterprise license in postgres collection

In the move from etcd to postgres it looks like the license server's record of the user's current enterprise license didn't get moved to postgres.

There's two places the license is stored:

In the license service, the user uploads a license and it's served to the enterprise services asynchronously in heartbeats. This needs to be durable.
In the enterprise service, we get the most recent license from the license server in the heartbeat and cache it in etcd. This is stored in etcd and cached in memory because this is how we enforce whether enterprise features are active.

There's two places the license is stored:

In the license service, the user uploads a license and it's served to the enterprise services asynchronously in heartbeats. This needs to be durable.
In the enterprise service, we get the most recent license from the license server in the heartbeat and cache it in etcd. This is stored in etcd and cached in memory because this is how we enforce whether enterprise features are active.

Yep thanks for clarifying. It was just lost on me reviewing the code here. Good catch fixing this!


Keyboard on android webview_flutter does not dismiss while input element blurs.

Flutter1.7.8+hotfix.3 fix problem that android keyboard does not display in webview, but remains a problem that the keyboard does not dismiss while input element blurs.

The keyboard in gif is dismissed by clicking back button, it ramains displayed while input blurs.

Flutter1.7.8+hotfix.3 fix problem that android keyboard does not display in webview, but remains a problem that the keyboard does not dismiss while input element blurs.

The keyboard in gif is dismissed by clicking back button, it ramains displayed while input blurs.

It's happening for me also, early response would be helpful.

Closing as a duplicate of flutter/flutter#36478


gpt4v refuse to answer/ insist on "I'm sorry, but I'm unable to view images" these kind of things

Thanks a lot for your effort!!!
Can I ask if you are experiencing gpt4v refusing to answer/insisting that there is no image provided when you validate gpt4v with mmmu?
I came across the issue above when I tried to send gpt4v the mmmu dataset...
Thanks a lot again!!!!!!!!!!

gpt4v is well aligned.
So better insist them to provide answers even gpt4v claims it cannot view images.

Thank you!!!


release 1.0: API make runtime args object opaque

Rather than making the runtime args opaque we introduced stl::span.   @pgkeller , let's sync on what else we need to change here.


Implement on-boarding carousell screen

Summary of Changes
This PR implements an on-boarding carousel page that can be used to provide useful information to the user the first time they use the application. Some of the changes in this PR are impermanent and just used for demonstration purposes, others need more scrutiny including:

I've restructured the globalStyles.ts so we can add theming for coming components like Buttons. I've also turned the colours into an object so we don't need to import them individually.
Added a Pagination.tsx file
Added an Onboarding.tsx file.

Images and changes to ContactStac.tsx are temporary.

Related Issues
Fixes #147
Pull Request Checklist
This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes. But please read our contribution guide at least once; it will save you a few review cycles!
If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this).
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components.
[x] Run prettier: npm run style-format
[x] Updated documentation for changed code and new or modified features.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
PR template adapted from the Python attrs project.

@amanji @NeilSMyers What do you two think of the direction of this PR? I think this will end up as a npm package to make it as easy as possible for implementers to create their own solution.

I think it's a good implementation. Later there's the option of enhancing it to pass pages directly as child components.

Only thing I'd say is try to remove any commented out code if it is un-used.

Removed the dead code. It was actually already gone I was just using to the wrong branch.

I've also generally followed the repo and used Props as the component props interface name. If we want to be more specific about naming props interfaces, we should probably align the other screens with that.

I'll align them with custom names. I wasn't sure if we over use Props if VSCode / TypeScript becomes less useful. Rather than say something is wrong with Props I'd rather see something is wrong with AuthStackProps. Not 100% its an issue.

Yeah thinking it's better to be more specific than have numerous Props results show up when searching.


SP5: LockedVertical / LockedHorizontal not working right

Bug Report
Issue: Using the code from the end of #3160, gives strange results. See screen shots below for various combinations and results.
Reproducing: Try code below, uncommenting the locking lines as required.
private void Form1_Load(object sender, EventArgs e) {

    double[] positions1 = { 1, 4, 7, 10, 13, 16, 19 };
    double[] values1 = { 1, 4, 7, 10, 13, 16, 19 };
    double[] positions2 = { 2, 5, 8, 11, 14, 17, 20 };
    double[] values2 = { 2, 5, 8, 11, 14, 17, 20 };

    BarPlot Plot1 = formsPlot1.Plot.Add.Bars(positions1, values1);
    BarPlot Plot2 = formsPlot1.Plot.Add.Bars(positions2, values2);

    formsPlot1.Plot.Axes.AutoScale();
    //formsPlot1.Plot.Axes.Rules.Add(new LockedVertical(formsPlot1.Plot.Axes.Left));
    //formsPlot1.Plot.Axes.Rules.Add(new LockedHorizontal(formsPlot1.Plot.Axes.Bottom));
}

Code as above, no axes locked:

Vertical axis locked:

Horizontal axis locked:

Both locked:

System Details

ScottPlot Version: 5.0.12-beta
Operating System: Windows 10
Application Type: WinForms
.NET Version: .NET 8.0

Thanks for reporting this! I figured out the problem is that the rules always copy the axis limits from the previous render onto the next, but if the plot never rendered then this weird bug occurs. I'll fix it now and it'll be in the next release 👍

This is pretty obscure, but technically it works with the current library if you call:
formsPlot1.Plot.Render();

instead of
formsPlot1.Plot.Axes.AutoScale();


了解到阿里有weex分发和预加载机制，请问这个方面后面有开源或开放计划吗，现在做的项目weex页面加载还是比较慢

weex页面每次加载的时候确实比较慢，尤其list页面，明显的延时，希望后期改进

同样遇到了这个问题！

我也知道这个方面能否给出解决方案，现在url加载是会有很明显的卡顿。

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


echo-bar displays with truncate-lines to nil the first time

💬 Description
echo-bar displays with truncate-lines to nil the first time. But once minibuffer is active, then the display error is gone.
📦 Related Packages

echo-bar

📝 Steps to reproduce

Start up Emacs
M-k M-p to enter *Packages* buffer
S-u to upgrade packages
if the prompt is exceeded to the window edge, then you should able to see the echo area is truncated.

🏡 Environments

Operating System: Windows 10
Emacs Version: 29.0.50
jcs Version: 8.2.2-snapshot
Terminal: N/A

🖼 Screenshots
WIP

Error is gone now.


Global configuration with optional override in functions

A global configuration table passed into the .setup method. For example (pseudo code):
require('reach').setup({
  global = {
    ...
  },
  buffers = {
    ...
  },
  marks = {
    ...
  },
  colorschemes = {
    ...
  },
  tabpages = {
    ...
  },
})

The functions used to open the pickers would then use the above configuration as a default except when additional options were given as parameters. For example:
require('reach').buffers({ show_current = false })

I don't see value in that. Users can store options in a variable, modify and extend them as they wish.
local options = {}
require('reach').buffers(vim.tbl_extend('force', options, { show_current = false }))

Why would anyone need to set options via setup function?


Rename getOuboundOverview to getOutboundOverview

Typo in Client.js:
    /**
     * Get overview statistics on Outbound Messages sent from the Server associated with this Client.
     *
     * @memberof Client.prototype
     * @method getOuboundOverview
     * @param {object} [filter] Optional filtering parameters.
     * @param {PostmarkCallback} callback A standard callback that is called when the API request completes.
     * @return {Promise} If no callback is passed, returns a Promise with the JSON response from the API (or error).
     */
    Client.prototype.getOuboundOverview = function(filter, callback) {
        callback = coalesceCallback(filter, callback);
        return this.processRequestWithoutBody('/stats/outbound', 'GET', filter, callback);
    };

fixed in the v2.0.0 of the library


[stable/mm-te] bump mm-te to 5.6.1

What this PR does / why we need it:
Bump mm-te to 5.6.1
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/lgtm


[BUG]: Bottom Spacing for results page

Description
This is a UI issue in the results page where the results page doesn't have a bottom spacing that separates it and gives room for the results actions to be scrollable and easy to see especially when the code block size is taking more height then the actions below it will be kinda hard to see especially that it will be so close to the page footer, image below shows this UI issue.
issue:

fix:

(optional) What browsers are you seeing the problem on?
Firefox, Chrome
Code of Conduct

[X] I agree to follow this project's Code of Conduct

created PR https://github.com/webdevcody/code-racer/pull/538

@Abdelmuttalib since the PR is merged pls close the issue