Month name not updating on language change

When I change my moment.locale() the days of the calendar update but month names don't unless I completely re-render my page. Is there something special about the way that calendar months are handled that I'm missing?

It seems we should probably be caching and checking the moment locale in shouldComponentUpdate (and anything else stateful about the moment singleton) on all our components.

@oldo how do you change the moment.locale()?
I'm trying a way to do it as well, but I don't find how .-.

Hi @oldo, have you looked at https://github.com/airbnb/react-dates/blob/master/stories/DateRangePicker.js#L67?

Thank you @majapw, it is easier than I have thought (-;

@willianribeiro I have the same problem, how did you fix It?

a medal of honor to @ian-rudge

@ian-rudge You are awesome
Thanks :)

I just add change locale.
startDate={moment(startDate).locale(i18n.language)}
endDate={moment(endDate).locale(i18n.language)}

I can't switch to pt-br either. I'm having a hard time understanding how to do this using moment in react-dates
<DateRangePicker
        startDatePlaceholderText="Ida"
        endDatePlaceholderText="Volta"
        showDefaultInputIcon
        orientation={orientation}
        withFullScreenPortal={withFullScreenPortal}
        startDate={startDate}
        startDateId="date-start-date"
        endDate={endDate}
        endDateId="date-end-date"
        onDatesChange={handleDatesChange}
        focusedInput={focusedInput}
        onFocusChange={(focusedInput) => setFocusedInput(focusedInput)}
        numberOfMonths={numberOfMonths}
        displayFormat="DD/MM/YYYY"
        dayAriaLabelFormat="DD/MM/YYYY"
        disabled={!isTwoWays && "endDate"}
      />

For those who are also having trouble getting it to work. Do as in the image and import this file below. Do this inside the component or page where you are importing the <DateRangePicker ... />. Put the code at the top.
localePtBr.ts file:
https://gist.github.com/pedropaulodf/30ef24887d250b6194b98a3ea2d4207d#file-localeptbr-ts

For those who are also having trouble getting it to work. Do as in the image and import this file below. Do this inside the component or page where you are importing the <DateRangePicker ... />. Put the code at the top.
localePtBr.ts file: https://gist.github.com/pedropaulodf/30ef24887d250b6194b98a3ea2d4207d#file-localeptbr-ts

thanks!! @pedropaulodf


input numeric how?

How to have a numeric input. that does not allow any letter in the input box.
I tried this

but it does not work. If I used a normal input text it works but in x-editable it does not work. Any ideas?

@liupangzi  and @chall8908 thanks both code is working

Hi there,
type: 'number', seems to work great for integers but is there any way to let it accept decimal values?
thanks!

Hi,
type="number" does work even though I get the following error in console
Uncaught InvalidStateError: Failed to execute 'setSelectionRange' on 'HTMLInputElement': The input element's type ('number') does not support selection.

Type = number will work. Just beware of browser issues. Not all browsers support that type. I think it is better to use the validation mentioned by @liupangzi


When deploying a large webjob, the file that keeps the webjob stopped is deleted and the webjob is restarted before deployment is completed

Required Information
Type: Bug
Enter Task Name: AzureRmWebAppDeploymentV4
Environment

Server - Azure Pipelines
account name: Mediaclip
team project name: Hub
build definition name/build number: Not sure

Agent - Private:
OS of the machine running the agent: 4.8-windowsservercore-2009
Agent version: 2.175.2

Issue Description
When deploying a large webjob (200mb+), the file that keeps the continuous webjob stopped( site\wwwroot\App_Data\jobs\continuous{jobname}\disable.job ) is deleted during the deployment, which restarts the webjob before deployment is completed, which locks the rest of the files that need to be deployed.
Note that the only setting that allowed us to make this work was "Exclude files from the App_Data folder", which isn't ideal since we may want to delete those files sometimes.
Task logs
ReleaseLogs_4247.zip
Error logs
2020-10-21T14:50:15.0613342Z ##[error]Error: Error Code: ERROR_FILE_IN_USE
More Information: Web Deploy cannot modify the file 'Mediaclip.ClipProducer.ProductionServer.exe' on the destination because it is locked by an external process.  In order to allow the publish operation to succeed, you may need to either restart your application to release the lock, or use the AppOffline rule handler for .Net applications on your next publish attempt.  Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_FILE_IN_USE.  Learn more at: https://go.microsoft.com/fwlink/?LinkId=221672#ERROR_FILE_IN_USE.
Error count: 1.
Edit: Changed the path for the file that disables the continuous job to the correct one

@Etiennepicard can you try using zip deploy option instead of web deploy

@Etiennepicard Web Deploy cleans target before deploying. "Exclude files from the App_Data folder" is the right approach to make it work. If you want to delete App_Data contents as well try Zip Deploy option. ZipDeploy doesn't remove all files from destination but replaces changed files and deletes removed files of package


DiskRP 2023-04-02 Changes

Related commands

az disk show [--disk-name]
[--ids]
[--resource-group]
[--subscription]
az disk create --name
--resource-group
[--accelerated-network {false, true}]
[--architecture {Arm64, x64}]
[--data-access-auth-mode {AzureActiveDirectory, None}]
[--disk-access]
[--disk-encryption-set]
[--disk-iops-read-only]
[--disk-iops-read-write]
[--disk-mbps-read-only]
[--disk-mbps-read-write]
[--edge-zone]
[--enable-bursting {false, true}]
[--encryption-type {EncryptionAtRestWithCustomerKey, EncryptionAtRestWithPlatformAndCustomerKeys, EncryptionAtRestWithPlatformKey}]
[--gallery-image-reference]
[--gallery-image-reference-lun]
[--hyper-v-generation {V1, V2}]
[--image-reference]
[--image-reference-lun]
[--location]
[--logical-sector-size]
[--max-shares]
[--network-access-policy {AllowAll, AllowPrivate, DenyAll}]
[--no-wait]
[--os-type {Linux, Windows}]
[--performance-plus {false, true}]
[--public-network-access {Disabled, Enabled}]
[--secure-vm-disk-encryption-set]
[--security-data-uri]
[--security-type {ConfidentialVM_DiskEncryptedWithCustomerKey, ConfidentialVM_DiskEncryptedWithPlatformKey, ConfidentialVM_VMGuestStateOnlyEncryptedWithPlatformKey, Standard, TrustedLaunch}]
[--size-gb]
[--sku {PremiumV2_LRS, Premium_LRS, Premium_ZRS, StandardSSD_LRS, StandardSSD_ZRS, Standard_LRS, UltraSSD_LRS}]
[--source]
[--source-storage-account-id]
[--support-hibernation {false, true}]
[--tags]
[--tier]
[--upload-size-bytes]
[--upload-type {Upload, UploadWithSecurityData}]
[--zone {1, 2, 3}]
[--elasticSanResourceId]
[--OptimizedForFrequentAttach]
az snapshot create --name
--resource-group
[--accelerated-network {false, true}]
[--architecture {Arm64, x64}]
[--copy-start {false, true}]
[--disk-access]
[--disk-encryption-set]
[--edge-zone]
[--elasticSanResourceId]
[--encryption-type {EncryptionAtRestWithCustomerKey, EncryptionAtRestWithPlatformAndCustomerKeys, EncryptionAtRestWithPlatformKey}]
[--for-upload {false, true}]
[--hyper-v-generation {V1, V2}]
[--incremental {false, true}]
[--location]
[--network-access-policy {AllowAll, AllowPrivate, DenyAll}]
[--no-wait]
[--public-network-access {Disabled, Enabled}]
[--size-gb]
[--sku {Premium_LRS, Standard_LRS, Standard_ZRS}]
[--source]
[--source-storage-account-id]
[--tags]
Describe the solution you'd like

"az disk show" should output LastOwnershipUpdateTime - a newly added property to a managed disk. This property shows the last time a disk transitioned in between the diskStates Attached/Detached/Reserved. Field is null on disk creation.
Below are the new parameters that need to be added for disk and snapshot creation commands:
az disk create --name
--resource-group `
[--elasticSanResourceId]
[--OptimizedForFrequentAttach]
az snapshot create --name
--resource-group
[--elasticSanResourceId]
Additional context

Customer can use ElasticSanResourceID to export Elastic San volume snapshot to managed disk resources
OptimizedForFrequentAttach property is used to skip fault domain alignment for the disk with the vm. This allows users to move the disk between vms in an availability set with no data move.
Once Customer provides ElasticSanResourceId parameter,
diskrpResource.properties.creationData.elasticSanResourceId needs to be set.
Similarly, if customer provides OptimizedForFrequentAttach parameter,
diskrpResource.properties.optimizedForFrequentAttach needs to be populated.
Link to the OpenAPI (swagger) spec:
https://github.com/Azure/azure-rest-api-specs/blob/82e7e30a6d46c095e0c3211f3ff7bafe82a362f1/specification/compute/resource-manager/Microsoft.Compute/DiskRP/stable/2023-04-02/diskRPCommon.json#L373
Link to our Powershell Github work version to this request:
https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/1377
Feature flags or restrictions on the changes provided in this design specification:
ElasticSanResourceId can only be used when a customer's subscription is whitelisted with Microsoft.Compute/ElasticSanImportExport” AFEC
Examples:
- az disk create -n diskName
-r resourceGroup
**-ElasticSanResourceId ""subscriptions/{subscription-id}/resourceGroups/myResourceGroup/providers/Microsoft.ElasticSan/elasticSans/myElasticSan/volumegroups/myElasticSanVolumeGroup/snapshots/myElasticSanVolumeSnapshot"

- az snapshot create -n snapshotName
-r resourceGroup
**-ElasticSanResourceId ""subscriptions/{subscription-id}/resourceGroups/myResourceGroup/providers/Microsoft.ElasticSan/elasticSans/myElasticSan/volumegroups/myElasticSanVolumeGroup/snapshots/myElasticSanVolumeSnapshot"

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

Added more info under Additional Context section.

@carlos6125 Could you please use this template [Microsoft Internal / Service Team] Feature Request to create this feature request? It contains more necessary information for us to develop, such as whether the SDK is ready

[--elasticSanResourceId]
[--OptimizedForFrequentAttach]

Please note that the parameter naming convention for CLI usually does not use camel case, but rather snake case, such as:
--elastic-san-resource-id and --optimized-for-frequent-attach

@carlos6125 Additionally, as our Ignite Sprint is already super fully scheduled (with a total of around 15 features and some top priority projects)
I'm concerned that we don't have enough time and energy to support this feature in this sprint. Is it acceptable if we plan the development and release of this feature for the next sprint (release date is 12-05)?

Created a new request using the template recommended. Closing this one.


Ignore QS on some sites in bookmarks

this would add custom logic which shouldnt be the case

this would add custom logic which shouldnt be the case


Make owned types (in same table) work in PostgreSQL.

Make owned types (in same table) work in PostgreSQL.
Fix identity annotation identification. Fixes #795 and #695 and #770 and #566 and regression from #772. With passing unit test.
@borisdj

I also discovered postgres integration doesn't properly implement "with graph" :-(

Thx for PR, Great work.
Merged and v6.5.5 published.
PS
Yes EF generated Sql is not always as expected, or as would a person write it directly.
Had similar issue before.
You can do first BulkInsert, then BulkRead.

There was a bug, regarding Identity column, introduced a few days ago with PR for MySql support.
I only found it this morning, it's now fixed so take the sync with latest source.


Nested configuration with both environmental and non environmental variables

I am trying to implement a configuration basically just like the Nested configuration example, with some environmental variables and some general ones.
So, with this:
  {
    "version": "0.1.0",
    "env": {
      "local": {
        "EnvironmentConfig": {
          "api": "http://localhost/"
        }
      },
      "production": {
        "EnvironmentConfig": {
          "api": "https://api.production.com/"
        }
      }
    }
  }

  gulpNgConfig('myApp.config', {
    environment: 'env.production'
  })

I was hoping I could get this:
angular.module('myApp.config', [])
.constant('EnvironmentConfig', {"api": "https://api.production.com/"})
.constant("version", "v0.1.0");

But I only get the environmental variable. So what is the point of having the nested environment or how can I get the non environmental variables to be added too?

Great question @RepoCorp, when you specify a value for environment, you're specifying where to find the data needed to generate the Angular constants.
In your example the environment data lives in env.production, so the plugin will read env.production and use that to generate the data.
It sounds like you're suggesting that the plugin should also "read everything inside env.production, along with any data in the JSON file that is outside env.production. Unfortunately that is a very large assumption this plugin is making and will differ from project to project.
For example, what if you didn't have a deeply nested configuration and it looked like:
{
  "production": {
    "foo": "bar",
  }
  "local": {
    "foo": "baz"
  }
}

With the current proposal we would end up with both configuration blocks being loaded when specifying environment: 'production'. In your example env.environmentA vs env.environmentB both share a common ancestor; that might not always be the case. Even if it did, how do we know how far up the tree to traverse? What if it was a.b.environmentA - do we look for other nodes in a? Do we continue to traverse upwards?
These are all assumptions the plugin would have to make -- often more risky than it might seem.

However I would like to support a scenario where there's environment specific data, and global data: What if you could specify multiple selection paths?
Imagine:
gulpNgConfig('myApp.config', {
  environment: ['env.production', 'version']
})

And that would:

Select data from env.production path
Also select any data from version
Allow you to specify as much or as little as you may need

☝ I think this could be a solution that would make both of us happy. What do you think?

That sounds perfect. Gives a lot of flexibility and control. 👍

I like this idea. Let's do it.
Do you have interest in adding this new functionality? Could be fun

I'll try 😄  Thank you!!

Great. Support for "nested environments" was added in #41. There may be some helpful code diffs in there that can point you in the right direction. It's here that we look at the environment setting to load the subset of JSON data https://github.com/ajwhite/gulp-ng-config/blob/develop/gulp-ng-config.js#L74-L76

Ok. I opened PR #61 with the changes. I haven't been working with Javascript for long and you have the honor 😉  to review my first contribution to an open source project ever! So feel free to change or discard anything, I will appreciate all the feedback.

:+1:  on this pr! I would like to use this

Support added in #61


Scale vertex lit lights by environment scale

Fixes: https://github.com/godotengine/godot/issues/29475
This is a bit of an ad hoc fix. Im not sure why the vertex lit lights need to be scaled this way, but it fixes the issue and matches the behaviour in both 3.1.1 and in GLES3.
Also moved the environment scaling for diffuse_toon to where it should be.

@reduz Do you already know when you will have time to approve this? We need this fix for our project and it would help to know when it will be merged to the master branch. Thank you all very much for your great work!

Thanks!

Wow, that was way faster than expected.
Thank you guys very much!


SAK-40068 - Update featherlight in PA system to one used in library

Thanks @mpellicer . I left some of the css in there still as it still looked like it helped make it look a little better, but most of this was just already in the global css. I just did minimal testing on it and it didn't seem to conflict with the featherlight you used but still better to just have one.


[BUG] Stock allocation quantity

Describe the bug
Before the recent update when you go to "Allocate Stock Item" Quantity field was filled up by default, now it shows "1".
Now you have to first check the quantity entered in the order and then manually enter it, and if you are entering it from more than one stock record you have to calculate the remaining amount, in the previous versions this was done automatically.
In addition to this, you can enter quantity greater than the one entered in the order, I believe this was not the case before.
To Reproduce
Steps to reproduce the behavior:

Create a new sales order
Enter a new part
Click the allocate stock icon
See error (Default quantity is 1 instead of the actual quantity in sales order)

Expected behavior
By default it should show the actual quanity required in the sales order, and if you have to enter quantity from more than one stock record it should acutomatically calculate the remaining quantity.
Screenshots

Deployment Method
Bare Metal
Version Information
Version Information:
InvenTree-Version: 0.6.0 dev
Django Version: 3.2.5
Commit Hash: 9fe1dd7be
Commit Date: 2021-10-19
Database: sqlite3
Debug-Mode: True
Deployed using Docker: False

@irameez yes, sqlite is a lot more lightweight than other databases such as mysql and posgres, in particular when running multiple concurrent queries.
I am considering moving to a different database architecture for the development instance as the speed improvements moving to e.g. mysql are significant.

@irameez I would never deploy with sqlite for production but for dev it makes everything very simple. In some environment's docker is not a feasible option.


Rework the Parse trait

It should just parse a Self -- no associated Self::Output type.

Coverage increased (+0.2%) to 73.109% when pulling 3089535ea5d36d227e456b482e74616ca986d2a2 on rework-parse-trait into eecaf7bee49b6beaec87f864fbc767bb3dd4f4ad on master.

Coverage increased (+0.2%) to 73.109% when pulling 3089535ea5d36d227e456b482e74616ca986d2a2 on rework-parse-trait into eecaf7bee49b6beaec87f864fbc767bb3dd4f4ad on master.


Introduce core module

@terjanq wrong PR?

What is  it PR at all?
I think my comment has been made by incident

PR === Pull Request

Oh yeah then, I don't know github stuff yet


Add solution for Partition Problem

Hey @wataridori, I'll do it. assign it to me

@Zaid23 Done,
Thank you very much ;)


Rerun a subset of keys

I want a version of shakeRunDatabase that takes in a set of rule keys to use as a dirtiness seed. Shake should then rerun only these rules and anything that depends on them, and assume that all other rule keys haven't changed.
The expected Shake overhead should be proportional to the number of rules dirtied and not to the number of rule dependencies.
It is ok if a Shake option is needed to enable this functionality and results in a higher space/time overhead in other operations

I assume that this will require extending Shake to track reverse dependencies. @hsenag given your dag experience, do you know what are the pitfalls here?

I have a rough, but working implementation of this. PR soon!

I assume that this will require extending Shake to track reverse dependencies. @hsenag given your dag experience, do you know what are the pitfalls here?

I guess the main thing is that it adds more overhead. Firstly the obvious point about space/time to store and update the reverse dependencies. But also having a bidirectionally connected graph significantly increases the chances of memory leaks and means you need more complicated locking and update protocols to avoid races. I don't know much about the Shake graph and haven't looked at the detail of your PR, though.


singularize "Transactions" yields "Tranaction"

Just found an oddity and thought I'd report it. This is as of 0.1.0 from hackage.
*Main> singularize "Transactions"
"Tranaction"

fixed in #2


Add advanced operator overloading and dunder methods overloading

Here's a comprehensive list of dunder methods that can be overloaded in Python:
Arithmetic Operators:
add: Addition (+)
sub: Subtraction (-)
mul: Multiplication (*)
truediv: True division (/)
floordiv: Floor division (//)
mod: Modulus (%)
pow: Exponentiation (**)
neg: Negation (-)
pos: Positive (+)
abs: Absolute value (abs())
invert: Bitwise inversion (~)
lshift: Left shift (<<)
rshift: Right shift (>>)
and: Bitwise and (&)
or: Bitwise or (|)
xor: Bitwise xor (^)
Comparison Operators:
eq: Equality (==)
ne: Inequality (!=)
lt: Less than (<)
le: Less than or equal to (<=)
gt: Greater than (>)
ge: Greater than or equal to (>=)
Container Operators:
len: Length (len())
getitem: Item access ([])
setitem: Item assignment ([])
delitem: Item deletion (del [])
contains: Membership test (in)
iter: Iterator (iter())
next: Next item (next())
Attribute Access:
getattr: Attribute access (object.attribute)
setattr: Attribute assignment (object.attribute = value)
delattr: Attribute deletion (del object.attribute)
Callable Objects:
call: Callable object (object())
String Representation:
str: String representation (str(object))
repr: Official string representation (repr(object))
Context Managers:
enter: Enter context (with object:)
exit: Exit context (with object:)
Pickling:
getstate: Prepare for pickling
setstate: Restore from pickled state
Other:
hash: Hash value (hash(object))
format: Format string (format(object))
sizeof: Size in bytes (sys.getsizeof(object))
reduce: Pickle representation
reduce_ex: Pickle representation with protocol version
By overloading these methods, you can customize the behavior of your custom objects and make them more Pythonic and intuitive to use.

How use use pickling? dunder methods
How to use getstate and setstate for pickling in Python:
Purpose:
__getstate__: Prepares an object for pickling by returning a dictionary containing the object's state.
__setstate__: Restores an object's state from the pickled data.
Usage:
Define __getstate__:
Implement the __getstate__ method within your class.
Return a dictionary containing the attributes you want to pickle.
Include only the attributes that are necessary for reconstructing the object.
Exclude attributes that are not pickleable or that should not be persisted.
Define __setstate__:
Implement the __setstate__ method within your class.
Take a dictionary as an argument.
Set the attributes of the object using the values in the dictionary.
Ensure that the dictionary keys correspond to the attributes you defined in __getstate__.
Example:
import pickle

class MyClass:
    def __init__(self, a, b):
        self.a = a
        self.b = b

    def __getstate__(self):
        return {'a': self.a, 'b': self.b}

    def __setstate__(self, state):
        self.a = state['a']
        self.b = state['b']

# Create an instance of MyClass
obj = MyClass(10, 20)

# Pickle the object
with open('my_object.pkl', 'wb') as f:
    pickle.dump(obj, f)

# Unpickle the object
with open('my_object.pkl', 'rb') as f:
    unpickled_obj = pickle.load(f)

print(unpickled_obj.a)  # Output: 10
print(unpickled_obj.b)  # Output: 20

How to add other type objects from right side of the operator

class P:
    def __init__(self, path: str) -> None:
        self.path = path

    def __add__(self, other: str) -> "P":
        return P(self.path + "/" + other)

    def __radd__(self, other: str) -> "P":
        return P(other + "/" + self.path)

    def __repr__(self) -> str:
        return f"P({self.path})"

p = P("santo")
p + "sajan"


feat: Allow excluding the Github Actor from the message

Issue
There is currently no way to exclude the Github Actor from being in the message.
Solution
According to the Slack API documentation, the author_link and author_icon values only work if author_name is present.
With omitempty specified on the author_name within the Attachment structure, allowing SLACK_MSG_AUTHOR to be an empty string will result in this field being unset which will allow users to choose if they want to exclude the Github Actor from being in the message.
Changes

Update main.sh to use = instead of :- on setting the GITHUB_ACTOR which avoids empty strings being substituted
Update README.md with details on how to avoid including the Github Actor in the message

Actually, I have successfully excluded it from the message by using ' ' as a value for SLACK_MSG_AUTHOR

Thanks @lazy-octopus-kebab , this works as a workaround:
env:
  SLACK_MSG_AUTHOR: ' '

But merging this PR would definitely help us too!


Analyze Yakindu SCT Qt timer leak

Note: This Qt timer service is originally generated by Yakindu SCT and not modified, yet.

Work in progress, need more time ...


Allow ':' in EndOfSentence rule - closes #1652

Codecov Report

Merging #1666 into master will increase coverage by 2.54%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1666      +/-   ##
============================================
+ Coverage     75.86%   78.41%   +2.54%
+ Complexity     1836     1634     -202
============================================
  Files           326      249      -77
  Lines          5507     4702     -805
  Branches       1002      883     -119
============================================
- Hits           4178     3687     -491
+ Misses          795      543     -252
+ Partials        534      472      -62

Impacted Files
Coverage Δ
Complexity Δ

.../detekt/rules/documentation/EndOfSentenceFormat.kt
95.23% <100%> (ø)
11 <0> (ø)
:arrow_down:

...tekt/formatting/wrappers/SpacingAroundOperators.kt

...h/detekt/formatting/wrappers/SpacingAroundComma.kt

...arturbosch/detekt/formatting/FormattingProvider.kt

...bosch/detekt/formatting/wrappers/ImportOrdering.kt

...tlin/io/gitlab/arturbosch/detekt/api/YamlConfig.kt

...in/io/gitlab/arturbosch/detekt/api/SplitPattern.kt

...n/io/gitlab/arturbosch/detekt/api/ConsoleReport.kt

...ekt/sample/extensions/rules/TooManyFunctionsTwo.kt

...turbosch/detekt/formatting/wrappers/PackageName.kt

... and 68 more

Continue to review full report at Codecov.

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


Catch null cases and default values to 0 to avoid exceptions that cause app to blow up.

Deploy preview for project-koku ready!
Built with commit 6459e2c4dd4ca72e18c302999274054714737064
https://deploy-preview-98--project-koku.netlify.com

Deploy preview for koku ready!
Built with commit 6459e2c4dd4ca72e18c302999274054714737064
https://deploy-preview-98--koku.netlify.com

LGTM :+1:


Proxy to all tg sesions

Hi. It will very good and nice to add to each session, prxoy . Even without username and password because in proxy provider we can add ip using without autorization. So please add posibility to add proxy to tg accounts. It is very hard to manage a lot of containers with one account. Thanks.

Hi,
Thank you for your suggestion.
I understand that managing multiple containers with one account can be challenging, and adding proxy support per session could help streamline your workflow. However, I'd like to share my perspective on this.
In my experience, I operate multiple Telegram accounts from a single IP address without any issues. This is actually quite common due to how ISPs manage their networks. For example, a mobile ISP like Vodafone UK has around 17 million subscribers but only a limited pool of IPv4 addresses. As a result, hundreds or even thousands of customers share a single public IP address using technologies like Carrier-Grade NAT (CGNAT). This means it's normal for many users to appear from the same IP without causing problems.
Imagine checking your game account on hotel Wi-Fi and getting banned because another guest is using the same game—that typically doesn't happen. From what I've seen, operating multiple accounts from one IP doesn't raise red flags.
Regarding adding proxy support to individual Telegram sessions, the third-party modules we use don't support multiple proxies easily. For instance:

Selenium: It can connect to a proxy but doesn't handle authentication with a username and password.
MITMProxy: We use this for modifying data (necessary for integrating certain games like Blum). It supports proxy authentication but only with one set of credentials at a time.

If you need different IP addresses for each Telegram account, here are a couple of options:

Paid Rotating Proxies: Use proxies that rotate IPs every so often. This can provide different IP addresses without additional configuration.
Multiple MITMProxy Instances: Start multiple instances of MITMProxy, each on a different port, and point different account sessions to each one. This can be achieved by:

Running separate containers for each account.
Replicating the repository into different directories and setting up each with a different port.

While I don't use proxies myself, I have added VPN tunnel authentication to the MITMProxy setup based on user requests to assist those who need it, such as those dealing with national-level firewalls. If users need further modifications based on their own assessment of risk, they can fork and modify the project, develop it, and contribute back. However, in terms of development by myself, I've provided what is there as a courtesy to those who want it but won't be spending any more time adding further support in the near future, and probably not ever.
I hope this helps clarify the situation. Please let me know if you have any other questions or need further assistance.
Cheers,
Phil


Unable to code in c language

Issue Type: Performance Issue
i have been trying very hard to use c language but there is always an error shows if i try to compile my code,  i am unable to make it interactive. I am unable to detect the issue. I tried various methods but nothing helps.
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
AMD Ryzen 5 5500U with Radeon Graphics          (12 x 2096)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.33GB (3.32GB free)

Process Argv
--crash-reporter-id 3bf1135c-611d-4cc9-b391-d154139f51bd

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	    94	 11488	code main
    0	   109	  1072	   gpu-process
    0	    83	  3080	   issue-reporter
    0	    26	  7016	   crashpad-handler
    0	   108	  8020	   shared-process
    0	    73	 14996	     fileWatcher
    0	    82	 15508	     ptyHost
    0	     6	  1548	       console-window-host (Windows internal process)
    0	     6	  1704	       console-window-host (Windows internal process)
    0	    66	 11184	       C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe
    0	    66	 12272	       C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe
    0	   169	 10144	   window (● #program to display the fibonacci series • Untitled-1 - Visual Studio Code)
    0	   157	 10632	   extensionHost
    0	   254	 11412	     "C:\Users\Hp\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node c:\Users\Hp\.vscode\extensions\ms-python.vscode-pylance-2022.6.20\dist\server.bundle.js --cancellationReceive=file:b47ede4d2b821be3d461da0308ff387607c4f91d5b --node-ipc --clientProcessId=10632
    0	    37	 14812	   utility-network-service

Workspace Info
;

Extensions (30)

Extension
Author (truncated)
Version

vscode-django
bat
1.10.0

doxdocgen
csc
1.4.0

vscode-html-css
ecm
1.13.0

code-runner
for
0.11.8

c-cpp-runner
fra
4.0.3

vscode-pull-request-github
Git
0.44.0

go
gol
0.33.1

better-cpp-syntax
jef
1.15.18

cpptask
kay
0.0.1

python
ms-
2022.8.0

vscode-pylance
ms-
2022.6.20

jupyter
ms-
2022.5.1001601848

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.8

cmake-tools
ms-
1.11.26

cpptools
ms-
1.10.7

cpptools-extension-pack
ms-
1.2.0

notepadplusplus-keybindings
ms-
1.0.7

powershell
ms-
2022.5.1

java
red
1.7.0

LiveServer
rit
5.7.5

pygame-snippets
tus
0.0.1

cmake
twx
0.0.17

vscode-lldb
vad
1.7.0

vscodeintellicode
Vis
1.2.21

vscode-java-debug
vsc
0.41.0

vscode-java-dependency
vsc
0.19.1

vscode-java-pack
vsc
0.23.0

vscode-java-test
vsc
0.35.0

vscode-maven
vsc
0.35.2

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdc:30486549

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Adding Doug Davis to list of project maintainers

Many thanks for submitting your Pull Request :heart:!
Please specify parts this PR updates:

[ ] Specification
[ ] Examples
[ ] Schema
[ ] Roadmap
[ ] Use Cases
[x] Community
[ ] Website
[ ] SDK
[ ] TCK
[ ] Other

What this PR does / why we need it:
Special notes for reviewers:
Additional information (if needed):

@duglin no objects I hope :)


Added Eclipse formatter

This closes #91

@calipee Can you please make your review for this issue?

@calipee Can you please make your review for this issue?

I added the comment but forgot to submit my review, I was already wondering why nobody replied for a week 😅


[BEAM-3637] Fix for HBaseIOTest - random table names for every test

We need to have clean HBase table for every test. Disabling and truncating/deleting is quite expensive operation on mini-cluster, it will add several seconds for every test. Instead, we can create new table with uniq name and it will be faster, especially for bunch of tests.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.

[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

retest this please

retest this please

Ok jenkins not happy but unrelated, so merging. Thanks again @aromanenko-dev


Identify code that could benefit from async / await

It looks like there are several people who love StackEdit and want it so badly, but are having some performance issues when they use it for projects that are larger than simple testing can reliably reproduce.
I think a good portion of these performance issues would go away if you identified bottlenecks, and rewrote their functionality to leverage the new async and await keywords.  (These keywords were added to JavaScript because there was demand for them, after all.)

I’m afraid performance issues are related to dom not JavaScript itself.


overlay: warn if overlay backing fs doesn't support d_type

- What I did
Print a warning if the backing fs for overlay/overlay2 doesn't support d_type.
Close #27358
Considering the discussion at https://github.com/docker/docker/issues/22937, the warning is not treated as an error.
However, I still think it is useful to treat it as an error in some future version (1.14? 1.15?).
Note that recent kernel prints a similar message: https://github.com/torvalds/linux/commit/e7c0b5991dd1be7b6f6dc2b54a15a0f47b64b007
However I think there are advantages to print the message as well in Docker:

Can support older kernels
Can be switched to an error in future Docker versions

- How I did it
Please refer to the source of pkg/fsutils.SupportsDType.
- How to verify it
For example, XFS with ftype=0 prints this warning.
$ qemu-img create /xfs-ftype0.img 10G
$ mkfs.xfs -m crc=0 -n ftype=0 /xfs-ftype0.img
$ mount -o loop /xfs-ftype0.img /mnt
$ dockerd -s overlay2 -g /mnt
The backing filesystem xfs does not support d_type. overlay2 won't work properly.

The warning should not be shown if ftype=1.
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)
TODO

[ ] PR for doc (after this PR gets merged)

Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

CC @rhvgoyal

/cc @dmcgowan @justincormack

If this is just a warning, then kernel is already emitting a warning. How does it help doing another one.

How does it help doing another one.

This was prompted by the issue here #27358. The warning should have been shown in the kernel but not is not somewhere users will look before filing an issue. However I am not convinced that adding a warning to the Docker logs will make this situation much better.
@AkihiroSuda what if instead we added a key mentioning d_type status to the the status output so when issues are filed it is easier to see the problem in the docker info output without making users dump their logs. My feeling here is we have to add something to make diagnosis easier, mentioning in the documentation and having warning in the logs can only go so far. I also don't see it as reasonable to someday flip this to an error, the kernel update to make this a warning was done because it had an impact on users, how would that impact change in the future?

@dmcgowan I guess we should decide how serious the situation is if someone runs docker without this. If it's a serious issue, then the overlay driver should probably be skipped (as "unsupported"), otherwise, we could output it as warning in docker info (where we already output various warnings if things are not supported). wdyt?

Updated PR

Now warning emits user-friendly guidance for xfs ("The backing filesystem seems formatted with f_type=0. Please reformat with f_type=1.")
Now docker info contains f_type Supported information

@rhvgoyal

This PR can support older kernel that doesn't print warning
This PR can provide user-friendly guidance ("The backing filesystem seems formatted with f_type=0. Please reformat with f_type=1.")

@dmcgowan
Makes sense, I added the information to docker info
@thaJeztah
IMO overlay is almost unuseful without d_type, and it should be an error after some "grace period" (1.14 or 1.15)

IMO overlay is almost unuseful without d_type, and it should be an error after some "grace period" (1.14 or 1.15)

If we are ok with doing that, we should add that in the warning ("running without t_type=0 will no longer be supported in 1.15" for example (needs a better sentence))

If this should be considered as a "feature deprecation", the warning should remain in v1.13, v1.14. and v.1.15. So the warning will be "running without t_type=0 will no longer be supported in 1.16" in such a case.
https://docs.docker.com/engine/#feature-deprecation-policy

Before an existing feature is removed it will be labeled as “deprecated” within the documentation and will remain in Docker for, usually, at least 3 releases. After that time it may be removed.

IMO this is not a "feature deprecation", because "supporting overlay without  d_type"  is a bug rather than a feature.
However, I'm ok to set the grace period (when the warning is changed to an error) to v1.16 so that it won't surprise users.

We discussed this, and suggest to:

make this show up in docker info
show a warning if it's not supported (as suggested above)
make this a "fatal" error in 1.16

This allows users that currently run without this being supported to migrate/address the issue

@thaJeztah thank you for making the discussion.
Updated PR and now the warning message is like this:
WARN[0001] overlay won't work properly because the backing filesystem xfs is not configured to support d_type. (The backing filesystem seems formatted with f_type=0. Please r
eformat the filesytem with f_type=1.) Note that this warning is planned to be treated as a fatal error in v1.16 .

Trying to see if we can make this more consistent with the devmapper dev-sync message;
devmapper: Udev sync is not supported. This will lead to data loss and unexpected
behavior. Install a dynamic binary to use devicemapper or select a different storage
driver. For more information, see https://docs.docker.com/engine/reference/commandline/daemon/#daemon-storage-driver-option

Perhaps (wrapped for readability):
WARN[0001] overlay2: the backing xfs filesystem is configured without d_type support,
which leads to incorrect behavior. Reformat the filesytem with f_type=1 to fix this
issue. Running without d_type support will no longer be supported in Docker 1.16.

@mstanleyjones perhaps you have suggestions?

Updated PR according to the suggestion from @mstanleyjones

ping @justincormack @tonistiigi PTAL

rebased to master
@justincormack @tonistiigi PTAL

ping @justincormack @tonistiigi

LGTM

LGTM


[FEATURE REQUEST]: Temporary marks, cycling through marks, telescope docs :)

Hello! I am a huge fan of harpoon in unending ways! There are, however, a couple things that have either always bothered me, or with the introduction of harpoon 2, have grated against my I-don't-like-github-or-twitter-but-love-rust bones. Lets start with the easiest one:
Cycling between marks. There should be three forms of cycling: cycling forwards in the harpoon list (like harpoon 1’s require("harpoon.ui").nav_next()), cycling backwards in the harpoon list (like harpoon 1’s require("harpoon.ui").nav_prev()), and finally, cycling between a set of specified marks. The first two are fairly simple, but the last gets a bit more needy. What I mean is being able to, through keybinds, easily select two items on your list, and then cycle between those. I would do this through some keybind that then accepts two numbers (where in the harpoon list the marks are), or a different keybind that just opens the menu and lets you select two marks. After that you can easily switch between these two files with a different api. This would be very useful if you have many files marked with harpoon, and then want to temporarily repeatedly switch between two specific files (instead of doing a split or something along those lines, one could also just use normal marks and c-6/c-^, but using harpoon would make the process more efficient).
Speaking of temporary stuff… temporary marks! When checking out plugins like trailblazer, one immediately notices that they are actually entirely unnecessary, apart from the wonderful, wonderful, feature that is temporary marks. What I mean is the ability to create a harpoon mark that gets destroyed the moment it is used. This would be wonderful. A alternative/extra feature would be the ability to toggle marks, which would have a similar effect.
Lastly, it would be wonderful to have a short description of how to integrate harpoon with telescope. Thank you very much for your patience, and have a wonderful, rust-based day.

I don't know what to do without nav_next and nav_prev

Lots of requests here:

nav_next / prev still exist in harpoon 2, though i think they are naughty

its not currently in the README yet
function HarpoonList:next()
    self._index = self._index + 1
    if self._index > #self.items then
        self._index = 1
    end

    self:select(self._index)
end

function HarpoonList:prev()
    self._index = self._index - 1
    if self._index < 1 then
        self._index = #self.items
    end

    self:select(self._index)
end

but those are functions directly off of the harpoon list object.

Creating a temporary list from a list, you should be able to harpoon -> telescope -> harpoon.  in fact, this functionality already works, someone just needs to create the telescope -> harpoon pathway and call

harpoon:list("foo"):resolve_display(items) will do that.

temporary marks... please use trailblazer, i don't think i'll add that functionality to harpoon

there is a harpoon telescope plugin within this project.  if you review that, it should give you enough information to be successful


Add 5 guardian public key examples to resources

Purpose
Currently it is not easy to run an example election due to guardian keys not having a way to register guardian keys. This provides guardian key examples in resources/guardians/*.pub.json. The contents of each can be serialized with the contract schema and registered as a guardian key directly in the contract (either through the sc-tools dapp or by any other means).
Changes

Convert deserialized guardian keys from bigint[] to number[] in voting dApp (as expected by election guard WASM module).

Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[ ] (If necessary) I have updated the CHANGELOG.

@mh-concordium for your reference (read the description 😄)


Problems with 21.4 / path

Our installation uses */otcs/cs.exe as basepath.
But the modules always tries */cs/cs

Thanks for the feedback - an option to configure that base_path was implemented today and will be part of the next release in the coming days.
Sample usage:
from pyxecm import OTCS

otcs_object = OTCS(
    protocol="https",
    hostname="otcs.fqdn",
    port="443",
    public_url="https://otcs.fqdn",
    username="admin",
    password="very-secret-value",
    base_path="/OTCS/cs.exe"
)

otcs_object.authenticate()

will be part of the next release

Great, thank you.

Version 1.4.0 has been released.
https://github.com/opentext/pyxecm/releases/tag/v1.4.0
https://pypi.org/project/pyxecm/
With this version we also make the documentation available:
https://opentext.github.io/pyxecm/pyxecm/otcs/#pyxecm.otcs.OTCS.__init__


Update replicate-data-microsoft-azure-sql-database.md

Update PS

@jolandaz
Thanks for the feedback. The changes have been confirmed and I've taken this content to live.


Fixture dependency on localization data

This fixture breaks oro install because it runs before required fixture. Without this, this fixture will fail due to missing language.

Thank you for your pull request.
It looks like this may be your first contribution to an Oro, Inc. open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at http://www.orocrm.com/contributor-license-agreement/
If you've already signed the CLA, it's possible we don't have your GitHub username or you're using a different email address. GitHub uses the email address you set in your local Git configuration to associate commits with your GitHub account. Please sign the CLA again using the correct GitHub username and email address or see this help article on setting the email on your git commits.
Once you've signed the CLA, please allow for some time for the submission to be processed.


bind-before-connect parameter

add connect_bindany parameter to change connect logic to backend
It permit to move the 64k local ports limit to 64k connections per destination.
The full explanation:
https://idea.popcount.org/2014-04-03-bind-before-connect/

I'm nixing this pull request for several reasons.
The idea is probably sound, but the implementation needs to be different.
In particular I don't like having the "magic" source address buried down in VTCP, since the exact same mechanism will be required if we want to control the outgoing address of backend connections.
So VTCP_Connect() should be given an optional "source suckaddr" parameter, and if present, it should bind(2) to that.
The other reason I'm nixing this is that this pull request is in the wrong github repos now.
Please head over to: https://github.com/varnishcache/varnish-cache which is now the official Varnish Project repository.


Add PowerISO to the list of utilities

Its not really an issue at all - it is just something that is installed since a lot of newer units do not have disc drives.
I love this repo, and am always happy to try and provide decent ideas for what could be an option
best regards

Why don't use the mount feature already integrated in Windows?

ngl I did not know I had an option for that, I will look into that - Thank you so much!


IllegalStateException: No script object associated with the Page

I guess it happens when

A page with frames is being parsed, and
One of frames changes URL
Then HtmlUnit tries to generate an "unload" event for the page which is not fully parsed yet (and therefore has getScriptableObject() == null).

I have a reproducible case in Selenide framework: https://github.com/selenide/selenide/blob/master/src/test/java/integration/FrameWaitTest.java
Try to run it several times: it fails time-to-time with the following error:
org.openqa.selenium.WebDriverException: java.lang.IllegalStateException: No script object associated with the Page. class: 'com.gargoylesoftware.htmlunit.html.HtmlPage' url: 'http://<IP_ADDRESS>:14702/page_with_frames.html' content: <!DOCTYPE html>
<html lang="en">
<head>
  <title>Test::frames</title>
  <meta charset="UTF-8">
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
</head>
<frameset rows="80,*" cols="*">
  <frame src="hello_world.txt" name="topFrame" id="top-frame" scrolling="no" noresize>
  <frameset cols="300,*">
    <frame src="page_with_dynamic_select.html" name="leftFrame" scrolling="no" noresize>
    <frame src="page_with_jquery.html" name="mainFrame">
    <frame src="page_with_parent_frame.html" name="parentFrame">
  </frameset>
</frameset>
</html>

Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'Andreis-MacBook-Pro.local', ip: 'fe80:0:0:0:4a3:96eb:183c:fbf%en0', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.14.6', java.version: '1.8.0_144'
Driver info: driver.version: HtmlUnitDriver
selenide.url: http://<IP_ADDRESS>:14702/page_with_frames_with_delays.html?browser=htmlunit&timeout=4000
selenide.baseUrl: http://<IP_ADDRESS>:14702

	at org.openqa.selenium.htmlunit.HtmlUnitDriver.get(HtmlUnitDriver.java:722)
	at org.openqa.selenium.htmlunit.HtmlUnitDriver.lambda$get$8(HtmlUnitDriver.java:687)
	at org.openqa.selenium.htmlunit.HtmlUnitDriver.lambda$runAsync$0(HtmlUnitDriver.java:429)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: No script object associated with the Page. class: 'com.gargoylesoftware.htmlunit.html.HtmlPage' url: 'http://<IP_ADDRESS>:14702/page_with_frames.html' content: <!DOCTYPE html>
<html lang="en">
<head>
  <title>Test::frames</title>
  <meta charset="UTF-8">
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
</head>
<frameset rows="80,*" cols="*">
  <frame src="hello_world.txt" name="topFrame" id="top-frame" scrolling="no" noresize>
  <frameset cols="300,*">
    <frame src="page_with_dynamic_select.html" name="leftFrame" scrolling="no" noresize>
    <frame src="page_with_jquery.html" name="mainFrame">
    <frame src="page_with_parent_frame.html" name="parentFrame">
  </frameset>
</frameset>
</html>

	at com.gargoylesoftware.htmlunit.html.DomNode.getScriptableObject(DomNode.java:922)
	at com.gargoylesoftware.htmlunit.javascript.host.event.Event.<init>(Event.java:215)
	at com.gargoylesoftware.htmlunit.javascript.host.event.BeforeUnloadEvent.<init>(BeforeUnloadEvent.java:69)
	at com.gargoylesoftware.htmlunit.html.HtmlPage.executeEventHandlersIfNeeded(HtmlPage.java:1217)
	at com.gargoylesoftware.htmlunit.html.HtmlPage.isOnbeforeunloadAccepted(HtmlPage.java:1291)
	at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:371)
	at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:315)
	at org.openqa.selenium.htmlunit.HtmlUnitDriver.get(HtmlUnitDriver.java:704)
	... 5 more

Hello
Did you solved the problem in any way. We have a similar problem in our selenium tests and don’t know how to fix it so far.

@Mahagoon no, we still haven't solved it. :(

Can you please provide the content of all the involveld artifacts (e.g. page_with_dynamic_select.html). I think i  found at least one place that might be the reason for that.
But i need to write a unit test to fix this finally.

@rbri Sorry, it was a flaky test, quite hard to reproduce.

Can i close this?

I need  an answer to this problem. this issue very important for me

Sorry but i need a case to reproduce this. Do you use the latest version of HtmlUnit?

@rbri hi. Sorry for the long delay. I will soon send you my code for reproducing the issue

great, thanks

I'm using the 2.33 version of HtmlUnit....

@rbri @BASSEMALMAHW Hi. I found a way to stably reproduce the problem:

git clone --branch reproduce-htmlunit-issue-68 https://github.com/selenide/selenide.git
cd selenide
./gradlew test

Expected output:

Task :test FAILED
200 tests completed, 12 failed

In the failed tests, you will see the error:

org.openqa.selenium.WebDriverException: java.lang.IllegalStateException: No script object associated with the Page. class: 'com.gargoylesoftware.htmlunit.html.HtmlPage' url: 'http://<IP_ADDRESS>:3834/hello_world.txt' content: Hello, WinRar!

Thanks for the test case, i can reproduce your results. Will try to make a plain HtmlUnit testcase out of this and hopefully this will still show the error.

@asolntsev @BASSEMALMAHW hve published a new snapshot build - can you please test if your problem is gone with this snapshot

And for documentation - this was a race condition; the page was available via window.getEnclosedPage before the page initialization was complete.

@rbri What version have you released?

I have tried net.sourceforge.htmlunit:htmlunit:2.45.0-SNAPSHOT, and got the same error:

java.lang.IllegalStateException: No script object associated with the Page. class: 'com.gargoylesoftware.htmlunit.html.HtmlPage' url: 'http://<IP_ADDRESS>:48612/page_with_jquery.html' content:

When I also added org.seleniumhq.selenium:htmlunit-driver:2.45.0-SNAPSHOT, all errors got fixed.

Yihhaaa!

Sounds strange - the fix is in HtmlUnit and not in the driver.

@rbri Well, it's probably because of transitive dependencies. htmlunit-driver:2.44.0 fetches some older versions of htmlunit-2.40.0.jar, neko-htmlunit-2.40.0.jar and htmlunit-cssparser-1.5.0.jar.

sounds reasonable - thanks


Update Sponsors section

A new design has been created for the sponsors' section.

Implement the design using css-grids.
Make sure the entire section is responsive and the order of sponsors as per the design.
Abstract the section as much as possible so that it is not bound to a particular layout and is easily responsive.
size of the logos starts decreasing from the top.
Maintain the ratio for boxes of gamma and delta sponsors.
instead of just 2 in a row for delta, possibly have 3. the gamma box should be flexible and the number of sponsors in a row should adjust as per the width.
For mobile view, it should be one below the other.

Interested.


Update dependencies to last versions

Did you check why sympy solver test is failing? Does this locally fail as well? (we don't change Sympy here and hence a bit confusing?)

Implemented via different PR.


Can't use example JSON payload for sending an Adaptive Card to an inbound webhook

We've been following the documentation example for "The flow for sending adaptive cards via an incoming webhook is as follows" but it's still not working. In Postman, we're getting a 400 error: "Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 400 with ContextId...".  Might inbound webhooks not accept Adaptive Cards as of September 18, 2020?

@cozimek - We are not able to reproduce the issue at our end. Also could you please share the requestbody and webhhok url?

While the webhook URL is private for our Teams channel and works properly for O365 Connector Cards, I can at least share the body of the Adaptive Card that we're trying to send via Postman.
{    "type":"message",    "attachments":[       {          "contentType":"application/vnd.microsoft.card.adaptive",          "contentUrl":null,          "content":{             "$schema":"http://adaptivecards.io/schemas/adaptive-card.json",             "type":"AdaptiveCard",             "version":"1.0",             "body":[                {                   "For Samples and Templates, see":"https://adaptivecards.io/samples"                }             ]          }       }    ] }

The adaptive card in the document is wrong. We are working on updating the card.
Could you please try this card:
{
   "type":"message",
   "attachments":[
      {
         "contentType":"application/vnd.microsoft.card.adaptive",
         "contentUrl":null,
         "content":{
            "$schema":"http://adaptivecards.io/schemas/adaptive-card.json",
            "type":"AdaptiveCard",
            "version":"1.2",
            "body":[
               {

            "type": "TextBlock",
            "text": "This is Adaptive Card",
            "weight": "bolder",
            "size": "medium"

               }
            ]
         }
      }
   ]
}

@Nikitha-MSFT it works! This is fantastic, thanks for the updated example.


Question about the run_transfuser.sh for evaluating transfuser agent

Hello! Thank you for your excellent work! I have a question about this line in the Transfuser evaluation script. It appears that the single_machine_thread_pool setting uses all available threads for evaluation. However, while the evaluation process runs in parallel on the CPU, it seems to utilize only a single GPU, which eventually leads to running out of single GPU memory.
Did I misconfigure something to distribute the parallel evaluation across multiple GPUs, or is it intended that the parallel evaluation process runs on just one GPU?
@DanielDauner Looking forward to your reply!

Hi @RexGPT
Thanks for your interest and this question!
Running evaluations in parallel over CPU and GPU processes simultaneously is tricky. We currently do not have a mechanism to run the PDM-Score and pre-processing on multiple CPU threads while only utilizing one GPU process. (I am no expert in this, but I'd assume this to be a challenge regarding syncing and communicating between CPU/GPU processes). As a result, finding the right worker (for CPU multiprocessing) and GPU utilization depends on your system specification.
In your case, you could try to reduce the parallel processes with worker.max_workers=N, where your model fits N-times into GPU memory. Using only the CPU for the evaluation can also be fast if you have many CPU cores and a lot of RAM, (e.g., with worker={ray_distributed, single_machine_thread_pool})
In the example script, we evaluated TransFuser on a system with 32 CPU threads, 32 GiB RAM, and 24 GiB GPU memory, where the standard setting was fairly fast and stable.
I hope that helps!
Daniel

Hi Daniel @DanielDauner  , thanks for your quick response! I’ve noticed that when using the SingleMachineParallelExecutor (worker=single_machine_thread_pool) worker, the maximum number of workers I can use on a 24GB GPU is 32, and the evaluation takes about 1 hour. However, when I switch to RayDistributedNoTorch (worker=ray_distributed_no_torch), I can set the worker count to 128, and it doesn’t require any GPU memory, reducing the evaluation time to around 30 minutes.
Is this expected behavior? From my comparison, it seems that the recommended worker=single_machine_thread_pool setting, which uses SingleMachineParallelExecutor, may not be the most efficient approach.

Yes and No. As I mentioned, using only the CPU for the evaluation (as done with worker={ray_distributed, ray_distributed_no_torch}) can be the fastest option. This setting however requires a lot of RAM, which is why I disabled for our system.
Generally speaking, if you can run any NAVSIM script with the ray library, it's very likely the fastest options. Downsides of ray are high RAM usage and instabilities (specifically on SLURM clusters).
I hope that helps!
Daniel

Thanks for your detailed reply!


Please change requirement of kaleido==0.2.1 to kaleido==0.2.1.post1

kaleido==0.2.1 cannot be installed:
ERROR: Could not find a version that satisfies the requirement kaleido==0.2.1 (from versions: 0.2.1.post1)
ERROR: No matching distribution found for kaleido==0.2.1

The version should be available.

Thanks for the quick response. It seems the version is not available for my architecture (arm v7), strange.


JWTDecode version conflicts with other package

Hi, is there any plan for us to update JWTDecode version to 3.1.0 in repack's podspec?
I am having problem when using this together with react-native-auth0 >= 3.0.0
Many thanks.
https://github.com/callstack/repack/blob/b0b8613eab82641e91607e0931eafc2360ff42a2/packages/repack/callstack-repack.podspec#L21C18-L21C39
[!] CocoaPods could not find compatible versions for pod "JWTDecode":
  In Podfile:
    A0Auth0 (from `../node_modules/react-native-auth0`) was resolved to 3.0.2, which depends on
      Auth0 (= 2.5.0) was resolved to 2.5.0, which depends on
        JWTDecode (~> 3.1)

    A0Auth0 (from `../node_modules/react-native-auth0`) was resolved to 3.0.2, which depends on
      JWTDecode (= 3.1.0)

    callstack-repack (from `../node_modules/@callstack/repack`) was resolved to 3.7.0, which depends on
      JWTDecode (~> 3.0.0)

Hi @allen012694,
as of right now, we can't bump the JWTDecode to 3.1.0 because it doesn't support iOS 12, which is a minimal deployment target for RN 0.72 & 0.71 which are still supported by Re.Pack.
Re.Pack states to support current + 2 last previous versions of RN. In 0.73 the minimal deployment target was changed to 13.4 so when RN 0.75 drops, we will be happy to update the JWTDecode library to the newest version.
To resolve your issue, I suggest using patch-package or something similar to modify the podspec for Re.Pack locally. I'm not a CocoaPods expert but I'm not sure there is any other way to resolve this at this moment.


[bug] Remaining bitcoin-core test fixes

There are a lot of bitcoin-core tests that are still failing. I created this file with all the failing tests.
The file contains all the failing tests from this file in bitcoin-core.

It will go through them one by one, and print something like this for each failed test :
  ScriptSig: '0x27 0x3024021077777777777777777777777777777777020a7777777777777777777777777777777701' -- ScriptPubKey: '0 CHECKSIG NOT' -- Flags: '' -- Expected: OK
  Expected : OK -- Result   : PANIC
  FAIL
scarb cairo-run --package shinigami_cmds '[[85638222473728638769160410210893464261263086061422684165462972715402475319,97557673223841770041305211021412912560163447137005097938746121282641147703],5288612062596008609236648564283419927782315402045370417,23,[],976111785041138328458856412106580,14,[],0,0]'
     Running shinigami_cmds
Running Bitcoin Script with ScriptSig: '0x27 0x3024021077777777777777777777777777777777020a7777777777777777777777777777777701', ScriptPubKey: '0 CHECKSIG NOT' and Flags: ''
Run panicked with [1637570914057682275393755530660268060279989363 ('Index out of bounds'), ].

showing the script that executed, the expected result and the result. The following lines give the scarb command needed to run the failing test manually. Most of the tests have a small bit of info inside the script_tests_failing.json file that explains what it is trying to test, which is usually a good hint for where to look.
The task would be to go through these and fix them. Thank you!
Using btcd in general is very useful for seeing bitcoin spec/code to understand how things may differ in our implementation, since our design is heavily inspired by the work there. But in particular this function will be super useful in seeing how they map errors to results from these bitcoin-core tests.

@bloomingpeach Could you comment here so I can mark you as working on this? Thank you!

@b-j-roberts can I work on this?

@b-j-roberts can i work on this?

For sure @SoarinSkySagar !

Hi @b-j-roberts, I think you closed this issue unknowingly because there are still some failing tests, which I'm currently working on.

Hi @b-j-roberts, I think you closed this issue unknowingly because there are still some failing tests, which I'm currently working on.

@SoarinSkySagar because you are writing the PR description "resolves #xxx", which will auto close the issue when the PR is merged. Best practice should be "This PR addresses #..." if that PR doesn't fully resolve the issue.

@SoarinSkySagar because you are writing the PR description "resolves #xxx", which will auto close the issue when the PR is merged. Best practice should be "This PR addresses #..." if that PR doesn't fully resolve the issue.

I see, will remember that from next time 😅
but can this issue be opened again? I've fixed one more test


🐞 Dagger doesn't respect SIGINT (ctrl-c)

What is the issue?
From @RonanQuigley

Dagger does not respect SIGINT (ctrl + c). Able to replicate on Mac and Linux.

We would request prioritising getting the SIGINT issue fixed ASAP. We found that it's a productivity killer (we made a lot of mistakes when making our pipelines, and having to kill the process manually each time gets tedious very quickly).

Log output
n/a
Steps to reproduce
run a pipeline and hit ctrl-c. It seems like SIGINT is ignored while the Dagger pipeline is running.
SDK version
Node.js SDK
OS version
mac, linux

@jpadams it seems like maybe this is specific to nodejs. We may just need to document the best practices for async processes in nodejs and how to handle process signals

Here's a code snippet to reproduce. Replicated with Dagger 0.4.2.
import * as dagger from<EMAIL_ADDRESS>
dagger.connect(
  async (client) => {
    await client.container().from('node').withExec(['']).stdout();
  },
  {
    LogOutput: process.stdout,
    Workdir: '.',
  }
);

You'll need to handle the graceful shutdown with process.on('SIGINT'). When running in k8s, you need process.on('SIGTERM')

Thanks @RonanQuigley for this reporting.
I've just opened a PR that should fix the issue:

#4911

This still appears to be an issue with the latest nodejs sdk.
To reproduce, run the github.com/dagger/examples/nodejs/react-build/build.js pipeline (update to latest sdk first). Once it starts running, ctrl+c. It'll keep running until it's done

SIGINT

This still appears to be an issue with the latest nodejs sdk.
To reproduce, run the github.com/dagger/examples/nodejs/react-build/build.js pipeline (update to latest sdk first). Once it starts running, ctrl+c. It'll keep running until it's done

Ok. Thanks @kpenfound for the heads-up. I'll tackle this one as soon as I can.

This still appears to be an issue with the latest nodejs sdk.
To reproduce, run the github.com/dagger/examples/nodejs/react-build/build.js pipeline (update to latest sdk first). Once it starts running, ctrl+c. It'll keep running until it's done

I have tried with the latest version of the SDK 0.6.0 and it seems to work 100% fine on my side

@grouville care to share a recording of how you confirmed the correct behaviour? Use whichever is easiest:

https://asciinema.org/ + https://lib.rs/crates/asciinema-scenario
https://github.com/saschagrunert/demo
https://www.loom.com/

@grouville care to share a recording of how you confirmed the correct behaviour? Use whichever is easiest:

https://asciinema.org/ + https://lib.rs/crates/asciinema-scenario
https://github.com/saschagrunert/demo
https://www.loom.com/

sure: https://www.loom.com/share/4919665f9f7e4aa2836b4582af97d54f.
Here I tested the build.js and build.mts

That was super helpful - thanks @grouville!
I just confirmed that this was an issue with<EMAIL_ADDRESS>
Fixed in Node.js SDK v0.6.0 👍

@kpenfound how should we keep the Dagger dependency updated in https://github.com/dagger/examples?


Vite + Tailwind + PostCSS Import - Internal server error

Describe the bug
Start w/ a default Vite (v2.6.14 + React) project.  Add tailwindcss and the postcss/postcss-import plugin.
Use an @import statement in the main .css file.  If there is an issue in the @imported CSS file, an exception will occur in the formatError function.
Run npm run dev and load the page.  An exception will occur in:
[vite] Internal server error: Cannot read properties of undefined (reading 'length')
      at posToNumber (./node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:4081:27)
      at generateCodeFrame (./node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:4106:13)
      at formatError (./node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:42239:42)
      at TransformContext.error (./node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:42185:19)
      at Object.transform (./node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:42399:25)
      at async doTransform (./node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:56801:29)

formatError is being called with:
error = {
  ...
  reason: `CssSyntaxError: ./src/styles.css:12:10: The `foobar` class does not exist.`,
  file: './src/styles.css',
  line: 12,
  column: 10
};

postition = undefined;

ctx = {
  ...
  _activeId: '/private/tmp/vite-issue/src/index.css',
  _activeCode: "@import './styles.css';\n"
}

Since ctx._activeId and ctx._activeCode don't actually reference the location of the error (instead they reference the top-level CSS file that @imported the problematic CSS file), generateCodeFrame ends up crashing.
Reproduction
https://github.com/scott-lc/vite-issue-20211111
System Info
System:
    OS: macOS 11.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 302.36 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: 1.22.15 - /usr/local/bin/yarn
    npm: 8.1.1 - ~/.nvm/versions/node/v16.13.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Chrome: 77.0.3865.120
    Firefox: 94.0.1
    Safari: 14.1.1
  npmPackages:
    @vitejs/plugin-react: 1.0.8 => 1.0.8
    vite: 2.6.14 => 2.6.14

Used Package Manager
npm
Logs
vite:config bundled config file loaded in 85.25ms +0ms
  vite:config using resolved config: {
  vite:config   plugins: [
  vite:config     'vite:pre-alias',
  vite:config     'alias',
  vite:config     'vite:react-babel',
  vite:config     'vite:react-refresh',
  vite:config     'vite:react-jsx',
  vite:config     'vite:modulepreload-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html-inline-script-proxy',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:client-inject',
  vite:config     'vite:import-analysis'
  vite:config   ],
  vite:config   server: { fs: { strict: undefined, allow: [Array] } },
  vite:config   resolve: { dedupe: [ 'react', 'react-dom' ], alias: [ [Object], [Object] ] },
  vite:config   optimizeDeps: {
  vite:config     include: [ 'react/jsx-dev-runtime' ],
  vite:config     esbuildOptions: { keepNames: undefined, preserveSymlinks: undefined }
  vite:config   },
  vite:config   configFile: '/private/tmp/vite-issue-20211111/vite.config.js',
  vite:config   configFileDependencies: [ 'vite.config.js' ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     server: { fs: [Object] }
  vite:config   },
  vite:config   root: '/private/tmp/vite-issue-20211111',
  vite:config   base: '/',
  vite:config   publicDir: '/private/tmp/vite-issue-20211111/public',
  vite:config   cacheDir: '/private/tmp/vite-issue-20211111/node_modules/.vite',
  vite:config   command: 'serve',
  vite:config   mode: 'development',
  vite:config   isProduction: false,
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     polyfillModulePreload: true,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {},
  vite:config     minify: 'esbuild',
  vite:config     terserOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     reportCompressedSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null,
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
  vite:config   },
  vite:config   env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen],
  vite:config     hasErrorLogged: [Function: hasErrorLogged]
  vite:config   },
  vite:config   createResolver: [Function: createResolver]
  vite:config } +3ms
  vite:deps Crawling dependencies using entries:
  vite:deps   /private/tmp/vite-issue-20211111/index.html +0ms
  vite:resolve 0.37ms /src/main.jsx -> /private/tmp/vite-issue-20211111/src/main.jsx +0ms
  vite:resolve 1.70ms react -> /private/tmp/vite-issue-20211111/node_modules/react/index.js +3ms
  vite:resolve 0.85ms react-dom -> /private/tmp/vite-issue-20211111/node_modules/react-dom/index.js +1ms
  vite:deps Scan completed in 26.96ms: {
  react: '/private/tmp/vite-issue-20211111/node_modules/react/index.js',
  'react-dom': '/private/tmp/vite-issue-20211111/node_modules/react-dom/index.js'
} +12ms
  vite:resolve 0.40ms react/jsx-dev-runtime -> /private/tmp/vite-issue-20211111/node_modules/react/jsx-dev-runtime.js +0ms
Pre-bundling dependencies:
  react
  react-dom
  react/jsx-dev-runtime
(this will be run only when your dependencies or config have changed)
  vite:resolve 0.12ms react -> /private/tmp/vite-issue-20211111/node_modules/react/index.js +0ms
  vite:resolve 0.94ms object-assign -> /private/tmp/vite-issue-20211111/node_modules/object-assign/index.js +1ms
  vite:resolve 0.56ms scheduler -> /private/tmp/vite-issue-20211111/node_modules/scheduler/index.js +29ms
  vite:resolve 0.99ms scheduler/tracing -> /private/tmp/vite-issue-20211111/node_modules/scheduler/tracing.js +1ms
  vite:deps deps bundled in 75.90ms +0ms
Port 3000 is in use, trying another one...

  vite v2.6.14 dev server running at:

  > Local: http://localhost:3001/
  > Network: use `--host` to expose

  ready in 309ms.

  vite:time 0.71ms / +0ms
  vite:spa-fallback Rewriting GET / to /index.html +0ms
  vite:time 18.62ms /index.html +34ms
  vite:resolve 1.00ms /@vite/client -> /private/tmp/vite-issue-20211111/node_modules/vite/dist/client/client.mjs +0ms
  vite:resolve 0.24ms /src/main.jsx -> /private/tmp/vite-issue-20211111/src/main.jsx +3ms
  vite:load 0.02ms [plugin] /@react-refresh +0ms
  vite:import-analysis 2.39ms [no imports] /@react-refresh +0ms
  vite:transform 5.14ms /@react-refresh +0ms
  vite:time 6.03ms /@react-refresh +41ms
  vite:load 9.46ms [fs] /@vite/client +6ms
  vite:resolve 0.68ms @vite/env -> /private/tmp/vite-issue-20211111/node_modules/vite/dist/client/env.mjs +13ms
  vite:resolve 0.18ms /node_modules/vite/dist/client/env.mjs -> /private/tmp/vite-issue-20211111/node_modules/vite/dist/client/env.mjs +0ms
  vite:import-analysis 3.95ms [1 imports rewritten] node_modules/vite/dist/client/client.mjs +8ms
  vite:transform 4.95ms /@vite/client +7ms
  vite:time 19.51ms /@vite/client +8ms
  vite:load 15.24ms [fs] /src/main.jsx +9ms
  vite:transform [reuse pending] for /node_modules/vite/dist/client/env.mjs +137ms
  vite:resolve 0.06ms react -> /private/tmp/vite-issue-20211111/node_modules/.vite/react.js?v=9d9b4eb8&es-interop +139ms
  vite:resolve 0.18ms /node_modules/.vite/react.js?v=9d9b4eb8&es-interop -> /private/tmp/vite-issue-20211111/node_modules/.vite/react.js?v=9d9b4eb8&es-interop +0ms
  vite:resolve 0.04ms react-dom -> /private/tmp/vite-issue-20211111/node_modules/.vite/react-dom.js?v=9d9b4eb8&es-interop +4ms
  vite:resolve 0.24ms /node_modules/.vite/react-dom.js?v=9d9b4eb8&es-interop -> /private/tmp/vite-issue-20211111/node_modules/.vite/react-dom.js?v=9d9b4eb8&es-interop +0ms
  vite:resolve 0.20ms ./index.css -> /private/tmp/vite-issue-20211111/src/index.css +1ms
  vite:resolve 0.13ms /src/index.css -> /private/tmp/vite-issue-20211111/src/index.css +0ms
  vite:resolve 0.03ms react/jsx-dev-runtime -> /private/tmp/vite-issue-20211111/node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8&es-interop +0ms
  vite:resolve 0.13ms /node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8&es-interop -> /private/tmp/vite-issue-20211111/node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8&es-interop +0ms
  vite:resolve 0.14ms /node_modules/.vite/react.js?v=9d9b4eb8 -> /private/tmp/vite-issue-20211111/node_modules/.vite/react.js?v=9d9b4eb8 +1ms
  vite:resolve 0.13ms /node_modules/.vite/react-dom.js?v=9d9b4eb8 -> /private/tmp/vite-issue-20211111/node_modules/.vite/react-dom.js?v=9d9b4eb8 +0ms
  vite:resolve 0.12ms /node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8 -> /private/tmp/vite-issue-20211111/node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8 +1ms
  vite:import-analysis 7.04ms [4 imports rewritten] src/main.jsx +145ms
  vite:transform 145.09ms /src/main.jsx +10ms
  vite:load 147.04ms [fs] /node_modules/vite/dist/client/env.mjs +146ms
  vite:import-analysis 0.02ms [no imports] node_modules/vite/dist/client/env.mjs +4ms
  vite:transform 0.16ms /node_modules/vite/dist/client/env.mjs +2ms
  vite:time 11.95ms /node_modules/vite/dist/client/env.mjs +148ms
  vite:load 1.47ms [fs] /node_modules/.vite/react.js?v=9d9b4eb8 +2ms
  vite:resolve 0.16ms ./chunk-NFTZ4EPM.js -> /private/tmp/vite-issue-20211111/node_modules/.vite/chunk-NFTZ4EPM.js +5ms
  vite:resolve 0.15ms /node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 -> /private/tmp/vite-issue-20211111/node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +1ms
  vite:import-analysis 0.88ms [1 imports rewritten] node_modules/.vite/react.js?v=9d9b4eb8 +2ms
  vite:transform 1.41ms /node_modules/.vite/react.js?v=9d9b4eb8 +2ms
  vite:load 3.72ms [fs] /src/index.css +2ms
  vite:load 5.57ms [fs] /node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8 +2ms
  vite:import-analysis 1.27ms [1 imports rewritten] node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8 +5ms
  vite:transform [reuse pending] for /node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +5ms
  vite:transform 1.60ms /node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8 +0ms
  vite:time 171.09ms /src/main.jsx +8ms
  vite:load 9.68ms [fs] /node_modules/.vite/react-dom.js?v=9d9b4eb8 +4ms
  vite:import-analysis 15.03ms [1 imports rewritten] node_modules/.vite/react-dom.js?v=9d9b4eb8 +34ms
  vite:transform [reuse pending] for /node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +34ms
  vite:transform 15.55ms /node_modules/.vite/react-dom.js?v=9d9b4eb8 +0ms
  vite:load 44.94ms [fs] /node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +38ms
  vite:import-analysis 0.48ms [no imports] node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +9ms
  vite:transform 0.79ms /node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +9ms
  vite:cache [memory] /node_modules/.vite/react.js?v=9d9b4eb8 +0ms
  vite:time 0.75ms /node_modules/.vite/react.js?v=9d9b4eb8 +43ms
  vite:cache [memory] /node_modules/.vite/react-dom.js?v=9d9b4eb8 +1ms
  vite:time 17.32ms /node_modules/.vite/react-dom.js?v=9d9b4eb8 +18ms
  vite:transform [reuse pending] for /src/index.css +36ms
  vite:cache [memory] /node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +35ms
  vite:time 1.61ms /node_modules/.vite/chunk-NFTZ4EPM.js?v=9d9b4eb8 +19ms
  vite:cache [memory] /node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8 +3ms
  vite:time 1.44ms /node_modules/.vite/react_jsx-dev-runtime.js?v=9d9b4eb8 +2ms
  vite:resolve 0.15ms ./styles.css -> /private/tmp/vite-issue-20211111/src/styles.css +0ms
3:01:08 PM [vite] Internal server error: Cannot read properties of undefined (reading 'length')
      at posToNumber (/private/tmp/vite-issue-20211111/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:4081:27)
      at generateCodeFrame (/private/tmp/vite-issue-20211111/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:4106:13)
      at formatError (/private/tmp/vite-issue-20211111/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:42239:42)
      at TransformContext.error (/private/tmp/vite-issue-20211111/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:42185:19)
      at Object.transform (/private/tmp/vite-issue-20211111/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:42399:25)
      at async doTransform (/private/tmp/vite-issue-20211111/node_modules/vite/dist/node/chunks/dep-e0fe87f8.js:56801:29)
  vite:time 2180.12ms /src/index.css +2s

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Possibly similar issue #1600

I've also been experiencing this issue. It can be quite frustrating because it makes it impossible to errors deriving from failed PostCSS compilation.
As a workaround, I'm using patch-package to patch posToNumber. My patch wraps this line in if (lines[i]). This is enough for me to see the error message, so I'm able to continue working, but I am certain that there must be a better solution.

Same here. Vite + tailwind + postcss import and I ran into the exact same error as described. Using latest versions of everything:

"postcss-import": "14.0.2",
"tailwindcss": "3.0.7",
"vite": "2.7.7",

https://github.com/vitejs/vite/blob/eb08ec5a838e13c75f6d034137d5835b44ecf279/packages/vite/src/node/server/pluginContainer.ts#L314
ctx._activeId is the original css file
when err is a error, err.file is the correct reported file by postcss which path needs to be normalized

How to fix this issue I have written tailwind CSS classes and followed all the instructions to run the command twice but still, it's not working? help please

@mahnoork18 fix will be released in 2.8


How do i find my  Client Launcher token and Fortnite Client Token.

I am new to fidler and i cant find my Launcher token

I found the way sorry.


[WIP] Adding users in bulk results in 504 error if >100 users are added in a single file

This is unfinished but I hope it won't take too much effort to finish. Feel free to grab me if you need an explanation.
Previously the users CSV was being uploaded and the users created synchronously. This was timing out.
My strategy has been to:

The admin uploads the Users CSV to S3 and sees a message saying the import will happen asynchronously
Create a job (UserImportJob) to download that file from S3 and pass it to Import::Users
Import::Users processes the users as before (unchanged)

There isn't loads left to do, as far as I can tell what's missing is:

Add a failure scenario to UploadUserList spec
Delete the temp Users CSV from S3 once the job is finished
Previously, errors in the CSV (e.g. incorrect column names; InvalidSalesforceId for users) were shown to the admin user right away on the page; now we need to pass them and log them somewhere and (presumably) tell the admin later on if a problem occurred.

Trello: https://trello.com/c/jIPnYVwo/1151-adding-users-in-bulk-results-in-504-error-if-100-users-are-added-in-a-single-file
Zendesk: 10303


Out-commented classes present

Reported by dietmarw on 30 May 2012 11:53 UTC
The Fluid/Sensors.mo file contains a number of classes that are out-commented. Either include them properly or remove them.

Migrated-From: https://trac.modelica.org/Modelica/ticket/754

Comment by dietmarw on 19 Sep 2012 08:26 UTC
Duplicate of #417

Changelog removed by dietmarw on 19 Sep 2012 08:26 UTC


Mention that XDG_CONFIG_HOME is respected on all platforms for configuration directory

The README currently reads as if the program does not respect the XDG_CONFIG_HOME variable, and instead uses the operating system specification for macOS and Windows. Where, in reality, the code appears to always check XDG_CONFIG_HOME first before defaulting to whatever else.

You're right. Thanks for the feedback. Will add that to the docs 🫡


build: separate webpack envs and generate smaller builds

This pr fixes the following issues:

[x] Remove the inline source map contained in the current bundle (reducing the bundle size from 612k to 136k)
[x] Separate webpack configurations according to the best practices
[x] Direct users to the minified bundle
[ ] Maybe we can further ignore the build folder since unpkg is sufficient to distribute bundles?

Please help test this pr, thanks!

Thank you for the building procedure.


Change uptime format in podman info to human-readable

Fixes #353
Before:  uptime: "1293018.35"
After:    uptime: 359h8m21.24s

Cloud podman failure is known, and the podman-in-podman tests are optional - Homu shouldn't block merge on it

@rh-atomic-bot r+

@rh-atomic-bot retry

Just trying to clear my overloaded inbox.  Could we tweak this from:
uptime: 359h8m21.24s
to
uptime: 359h 8m 21.24s
just adding spaces.  Adding days would be nice too if possible.  i.e.:
uptime: 14d 23h 8m 21.24s
I'm happy to play with it if you'd like.

@TomSweeneyRedHat Sure. You'd have to do a custom string format (Go provides functions to get years/weeks/days/months/seconds out of a Duration, but you'd need a lot of conditionals if we don't want to print "0 years 0 weeks 0 days...") but it shouldn't be difficult. Could be a fair bit of code in pure number of lines to handle those conditionals though.

OK, I'll give it a whack.  Should be a fun side project.


update privacy policy

I have added some text in the privacy policy section.

Share the link.

https://codervivek5.github.io/HealhUb/

You have done a good job.


Fix sidebar not going all the way to bottom of page

When you scroll to the bottom of the page the sidebar doesn't take up the whole height of the screen.

The new sidebar fixed this issue


Declarative configuration of initrd networking

Followup of https://github.com/NixOS/nixpkgs/pull/12795. tl;dr: Configuration of initrd networking via NixOS options is a good idea, but there are several questions:

Do we still want to have ip=? There might be other people already using it, so we should be careful to not break their (remote!) setups.
We wouldn't be able to have 100% consistency because networking has too many things inside (firewall, WLAN, virtual interfaces -- to name a few) that we can't (and don't want) to bring inside initrd. So we need to somehow document what options are supported in initrd and what are not. One solution may be to have all supported settings duplicated in a distinct boot.initrd.network namespace, but it's not ideal.

The current ip=... option is at least problematic since the same option is used by the kernel's IP autoconfiguration (which is not currently enabled in our kernels, though, but I might want to try that someday).

FWIW I've taken that approach from Arch Linux; they use it instead of kernel IP autoconfiguration for the same tasks (NFS roots, for example) for some reason. Personally I think that configuration like this should be done in userspace and not in the kernel, but I don't have any strong preference.

Regarding 1), we never had ip= in a stable branch so I don't think we need to support it.
Regarding 2), it's probably enough to support DHPC and basic static interface configuration.

in one of my setups, i'm needing bridging and static IP at the initrd stage

I guess this is another thing where using dracut for the initrd could potentially help.

triage: is there something that can or should be done here?

https://nixos.org/nixos/options.html#boot.initrd.network looks like it can only do dhcp at the initrd level right now, static ip and bridge stuff is still missing

This is still important.


Automagically subscribe all fetched items and keep it in sync with the server?

Is it possible to setup subscriptions for all cached items so that whenever any of those items was changed on the server, it will be updated on the local too?

This sounds outside the scope of apollo-link-state, may want to look into something like Firebase (https://firebase.google.com/)

or possibly #138


Add calico-dcos v3

Calico v3 introduces Calico v2.0 to DC/OS, running our latest platform release of calico services.

@djosborne Can I also ask you to write short getting started doc for this package so users don't have any issues installing and understanding how they work?
You can create a PR against https://github.com/dcos/examples and refer other examples listed there. These examples will finally go here: https://dcos.io/docs/1.8/usage/tutorials/.
This is also now part of the package submission guidelines: https://github.com/mesosphere/universe#submit-your-package

@djosborne @ryadav88 most of what's needed is already on Calico's documentation, so it should be mostly a format change. But some users have reported in the past issues with the installation process in your website, so this would be a good time to provide a tested&verified "from zero to hero" official installation process. I volunteer to provide a test cluster so that we can test this on a real setup and not on a Vagrant thingy. Ping me on email and let's make it happen.

@ryadav88 @fernandosanchezmunoz We have a Calico-DC/OS install guide, but it's out of date / could use a revision.
http://docs.projectcalico.org/v2.0/getting-started/mesos/installation/dc-os/framework
I'll clean it up and then ping you guys.

@ryadav88 @fernandosanchezmunoz
Here's the updated DC/OS Install Guide:
http://docs.projectcalico.org/v2.0/getting-started/mesos/installation/dc-os/framework
And the Installation Customization Guide:
http://docs.projectcalico.org/v2.0/getting-started/mesos/installation/dc-os/custom

@ryadav88 @fernandosanchezmunoz ping

@djosborne I'll review it today.

Here's the updated DC/OS Install Guide:
http://docs.projectcalico.org/v2.0/getting-started/mesos/installation/dc-os/framework
And the Installation Customization Guide:
http://docs.projectcalico.org/v2.0/getting-started/mesos/installation/dc-os/custom

@djosborne looks like this is still the old documentation based on version 0.3.1. Please update it to add steps for the latest version (how to access the service UI... ) and you can use the same content to create a PR against https://github.com/dcos/examples. By maintaining an example in that repo we can always make sure that updates to packages work with the new versions of dc/os and new users don't have problem understanding what the package is and how to install/run it.
Apart from this, the PR LGTM. I would like to test the instructions in the example before merging this PR.

@ryadav88 I updated the install images so they included the correct version string and show the new services UI. But I don't have the bandwidth to move the install docs to dcos/examples at the moment, as they'd also need some adjustments to fit that repository and link appropriately to the existing calico documentation.
Can we merge this update now and look to move that documentation in the future?

@ryadav88 I updated the version string and services UI in the images.
I also copied our documentation and opened a PR here: https://github.com/dcos/examples/pull/45


Using useContext in component breaks hot reloading.

Describe the bug
When I added useContext to my component, I got the following error on hot-reload:

Your Example Website or App
Part of my pr: https://github.com/webxdc/store/pull/158
Steps to Reproduce the Bug or Issue

cd frontend && pnpm i && pnpm dev
change some class or so in Info component

Expected behavior
No error
Screenshots or Videos
No response
Platform
OS: Manjaro Linux x86_64
Kernel: 6.1.31-2-MANJARO
Additional context
No response

Can you link it to the file of the code where it happens

Closing as stale


need setPreventMinimize and setPreventMaximize

when the app is alwaysOnTop and then minimize the app,  unable to open the app again.
on MacOS 13+ with 'Foreground Priority Boost' open

I need it too


fix be pod error log-storage-name and annotations

fix be pod error log-storage-name and annotations
Signed-off-by: haiming<EMAIL_ADDRESS>

thanks for the fix!


Remove redirect and point to the generated kubectl doc directly

Since we now generate the kubectl doc for each release, it is no longer necessary to use the old redirects. Cleaning up the references throughout the documents.

@tengqm Please take a look at this one.

/assign @heckj

/lgtm
/approve


Pedestrian area outer relation with grass/forest inners buggy

Describe the bug
Some locations like this https://streets.gl/#44.94065,-123.02938,22.75,202.50,222.36 render properly in f4 and in 2d but not in Streets-GL -- it's as though the southerly half of the capitol mall is clipped or failed to load some/all vector points despite the loaded and unloaded parts having no discernible differences.
Expected behavior
Consistency with iD, Carto, F4map, etc
Map location
https://streets.gl/#44.94065,-123.02938,22.75,202.50,222.36
Screenshots

System information

OS: Windows 11
Browser with version: Firefox 112.0.2 (64-bit)

Where things seem to go wonky is where a footway is mapped on top of a road on layer=-1. Loaded the area into JOSM and ran validator spitting out 65 issues, so not all is mapped text book.

PS, I'm impressed though with the backrested benches all facing in the park at both sides without any direction tags.

Unsure how else to tag it, the two features are colinear and only separated vertically. I don't see any JOSM issues that seem like they'd affect this, most seem to be cosmetic/pedantic or relating to building:parts inside of buildings. JOSM does complain that we're using highway=pedestrian + area=yes instead of the apparently updated area:highway=pedestrian tagging scheme, but JOSM itself doesn't even render area:highway=pedestrian and the wiki acknowledges that the current tagging is correct (large areas where pedestrians can walk any way they want, like a square or plaza)

JOSM does complain that we're using highway=pedestrian + area=yes ("area on a relation") instead of the apparently updated area:highway=pedestrian tagging scheme

I don't use JOSM, but I don't think it complains of highway=pedestrian+area=yes instead of area:highway=pedestrian, but more likely about the fact that every multipolygon is an area, so tagging it is redundant.

Another example of a multipolygon is missing its innner cutout is https://streets.gl/#49.84893,9.96558,45.00,0.00,258.67 (i.e. the round building should have an open atrium)

Another example of a multipolygon missing its innner cutout is https://streets.gl/#49.84893,9.96558,45.00,0.00,258.67 (i.e. the round building should have an open atrium)

This is because roof:shape=pyramidal doesn't respect multipolygon holes. For this particular building you should probably use roof:shape=hipped.

I tried roof:shape=hipped. It cuts the hole, but the roof is flat. (Maybe related to #1 ?)
Also, in F4, the roof looks very wonky.
Thinking about it, roof:shape=skillion seems more appropriate. Hole is there, but also flat roof.

roof:shape=hipped is not guaranteed to work sadly. It often fails on polygons with holes, especially on donut-like multipolygons like this one.


why when downloading the worst quality video it becomes 3gp not video+audio dash

Checklist

[x] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.01.21. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[ ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[ ] I've read the guidelines for opening an issue

Description
why yt-dlp -f "wv*+wa" not working properly, for example, when I download a video with the worst quality, it downloads in 3gp format, not video+audio?
Verbose log
[debug] Home config "yt-dlp.conf": ['-i', '--hls-prefer-native', '--remux-video'
, 'mp4', '-f', 'wv*+wa/w', '-N', '10', '--fragment-retries', 'infinite', '--outp
ut', '%(playlist)s/%(title)s.%(ext)s', '-vU']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8 (No ANSI), err utf-8 (No A
NSI), pref cp1252
[debug] yt-dlp version 2022.01.21 [f20d607] (win_exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg n4.4.1-3-gb9e6f19095-20211123 (setts), ffprobe 4.4-
full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2022.01.21, Current version: 2022.01.21
yt-dlp is up to date (2022.01.21)

You thin 3gp is not worse quality than the other formats?

not what I mean is the merge video+audio feature with use yt-dlp -f "wv*+wa" but what I download is only 3gp, not video+audio?

Remove the * if you want to guarantee separate video and audio downloads

how to use [height<=129] for audio 129k

-f ba[abr<=129k]