Unable to restore a MySQL backup when no database is specified

We were trying to restore a full MySQL backup but mysql complains with this error: Can't create table mysql.db (errno: -1 "Internal error < 0 (Not system error)"). We checked the dump file and it contains the DROP and CREATE statements for the tables.
We ran some more tests but specifying the database and it works fine.
Using shield 0.8.1. Full log:
UUID:         3e7ded34-691b-45a7-9141-a858869d9aac
Owner:        ubuntu@
Type:         restore
Status:       failed

Started at:   Wed, 01 Feb 2017 10:52:37 +0000
Stopped at:   Wed, 01 Feb 2017 10:52:37 +0000

Archive UUID: 4a801111-0b83-4f82-b27c-edf4d6a7726a

Log:          Validating environment...
              =========================
              SHIELD_OP ... found
              SHIELD_STORE_PLUGIN ... found
              SHIELD_STORE_ENDPOINT ... found
              SHIELD_TARGET_PLUGIN ... found
              SHIELD_TARGET_ENDPOINT ... found
              SHIELD_RESTORE_KEY ... found
              OK

              Validating TARGET plugin `mysql`...
              ===================================
              DEBUG> 'validate' action requested with options plugin.PluginOpts{Debug:false, Version:false, Action:"validate", Info:struct {}{}, Validate:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:"{\"mysql_user\":\"root\",\"mysql_password\":\"<REDACTED>\",\"mysql_host\":\"<REDACTED>\",\"mysql_post\":\"3306\"}"}, Backup:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Restore:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Store:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing store endpoint'\"" }{Endpoint:""}, Retrieve:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing retrieve endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to retrieve from storage'\"" }{Endpoint:"", Key:""}, Purge:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing purge endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to purge from storage'\"" }{Endpoint:"", Key:""}}
              ✓ mysql_host          <REDACTED>
              ✓ mysql_port          using default port 3306
              ✓ mysql_user          root
              ✓ mysql_password      <REDACTED>
              ✓ mysql_read_replica  no read replica
              DEBUG> 'validate' action returned <nil>
              OK

              Validating STORE plugin `s3`...
              ===============================
              DEBUG> 'validate' action requested with options plugin.PluginOpts{Debug:false, Version:false, Action:"validate", Info:struct {}{}, Validate:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:"{\"access_key_id\":\"<REDACTED>\",\"bucket\":\"epc-poc\",\"prefix\":\"backups\",\"secret_access_key\":\"<REDACTED>\",\"signature_version\":\"4\",\"s3_host\":\"s3.amazonaws.com\"}"}, Backup:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Restore:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Store:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing store endpoint'\"" }{Endpoint:""}, Retrieve:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing retrieve endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to retrieve from storage'\"" }{Endpoint:"", Key:""}, Purge:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing purge endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to purge from storage'\"" }{Endpoint:"", Key:""}}
              ✓ s3_host              s3.amazonaws.com
              ✓ access_key_id        <REDACTED>
              ✓ secret_access_key    <REDACTED>
              ✓ bucket               epc-poc
              ✓ prefix               backups
              ✓ signature_version    4
              ✓ socks5_proxy         (no proxy will be used)
              ✓ skip_ssl_validation  no, SSL WILL be validated
              DEBUG> 'validate' action returned <nil>
              OK

              Running restore task (using bzip2 compression)
              ==============================================
              DEBUG> 'restore' action requested with options plugin.PluginOpts{Debug:false, Version:false, Action:"restore", Info:struct {}{}, Validate:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Backup:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Restore:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:"{\"mysql_user\":\"root\",\"mysql_password\":\"<REDACTED>\",\"mysql_host\":\"<REDACTED>\",\"mysql_post\":\"3306\"}"}, Store:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing store endpoint'\"" }{Endpoint:""}, Retrieve:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing retrieve endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to retrieve from storage'\"" }{Endpoint:"", Key:""}, Purge:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing purge endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to purge from storage'\"" }{Endpoint:"", Key:""}}
              DEBUG> MYSQL_USER: 'root'
              DEBUG> MYSQL_PWD: '<REDACTED>'
              DEBUG> MYSQL_HOST: '<REDACTED>'
              DEBUG> MYSQL_PORT: '3306'
              DEBUG> MYSQL_READ_REPLICA: ''
              DEBUG> MYSQL_DB: ''
              DEBUG> MYSQL_BIN_DIR: '/var/vcap/packages/shield-mysql/bin'
              DEBUG> Exec: /var/vcap/packages/shield-mysql/bin/mysql  -h <IP_ADDRESS> -P 3306 -u root
              DEBUG> Executing '/var/vcap/packages/shield-mysql/bin/mysql' with arguments [-h <IP_ADDRESS> -P 3306 -u root]
              DEBUG> 'retrieve' action requested with options plugin.PluginOpts{Debug:false, Version:false, Action:"retrieve", Info:struct {}{}, Validate:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Backup:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Restore:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing backup target'\"" }{Endpoint:""}, Store:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing store endpoint'\"" }{Endpoint:""}, Retrieve:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing retrieve endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to retrieve from storage'\"" }{Endpoint:"{\"access_key_id\":\"<REDACTED>\",\"bucket\":\"epc-poc\",\"prefix\":\"backups\",\"secret_access_key\":\"<REDACTED>\",\"signature_version\":\"4\",\"s3_host\":\"s3.amazonaws.com\"}", Key:"backups/2017/02/01/2017-02-01-105209-4bc2b5f6-6f0c-468a-abc3-b2deafa3a371"}, Purge:struct { Endpoint string "goptions:\"-e, --endpoint, obligatory, description='JSON string representing purge endpoint'\""; Key string "goptions:\"-k, --key, obligatory, description='Key of blob to purge from storage'\"" }{Endpoint:"", Key:""}}
              DEBUG> 'retrieve' action returned <nil>
              ERROR 1005 (HY000) at line 93: Can't create table `mysql`.`db` (errno: -1 "Internal error < 0 (Not system error)")
              DEBUG> 'restore' action returned plugin.ExecFailure{Err:"Unable to exec '/var/vcap/packages/shield-mysql/bin/mysql': exit status 1"}
              TASK FAILED!!  shield worker 3 failed to execute the command against the remote agent <REDACTED>:5444 (Process exited with: 3. Reason was:  ())
              Unable to exec '/var/vcap/packages/shield-mysql/bin/mysql': exit status 1

              EXITING 3

We're running more experiments, trying to recreate what shield is doing, and got the same problem.
Interestingly, we have created manually a table inside the mysql database. Then dumped all databases, and then the restore command works.
We will try to run more experiments.

Thanks for reporting this and giving detailed information, I will look into it.

Just one more note, we are trying to backup the databases created by the cf-mysql-release.

this might be a problem:
shield worker 3 failed to execute the command against the remote agent <REDACTED>:5444

The shield daemon expects a hostname:port or ip:port of a running shield-agent to go run the backup/restore.
I will keep digging, but it is possible the shield daemon is trying to connect to :5444 and is failing

Yep, I updated the IP address with <REDACTED> :)
I can confirm the shield-agent was running and was executing the task.

If you are getting Can't create table mysql.db (errno: -1 "Internal error < 0 (Not system error)") -- there should be useful information about the mysql failure in the mysql.log file.  Anything there, like stack traces, that could help troubleshoot this?

Thanks. Tomorrow weI'll look into the mysql logs. We'll also try the xtrabackup plugin.

We tested today the xtrabackup plugin and it worked seamlessly, so I'm closing this issue.


Do not allow multiple state machines with the same ID (close #489)

Addresses issue #489
The change automatically removes previous state machine (if any) with the same identifier when adding a new one. This prevents multiple of the same context being added to events in case the same state machine is registered multiple times.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

@AlexBenny That's a really good point, thanks! I updated the StateManager to check for the type of state machine being replaced and do nothing in case it is being replaced with one of the same type. Please take another look at it when you have the chance to see if it's okay.


wayfire: init at 0.3.1

Motivation for this change
Package the wayfire 3D wayland compositor, including its config library and shell (panel, background). Seems to work fairly well using the default/example config files.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Hi, just a quick heads up: The build will fail with wlroots 0.9.1:
[47/157] Compiling C++ object 'src/25a6634<EMAIL_ADDRESS>../src/main.cpp: In function 'int handle_config_updated(int, uint32_t, void*)':
../src/main.cpp:47:9: warning: ignoring return value of 'ssize_t read(int, void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   47 |     read(fd, buf, INOT_BUF_SIZE);
      |     ~~~~^~~~~~~~~~~~~~~~~~~~~~~~
[71/157] Compiling C++ object 'src/25a6634<EMAIL_ADDRESS>FAILED: src/25a6634<EMAIL_ADDRESS>/nix/store/a9hbzlkdfvpr4r8mjwcxcda9smjp5v1i-gcc-wrapper-9.2.0/bin/c++ -Isrc/25a6634@@wayfire@exe -Isrc -I../src -I. -I../ -I../src/api -I/nix/store/yrjafz94aqjdrm28bwbmxng8qw59xk93-wayland-1.17.0/include -I/nix/store/irxs7gzpwmsav6739mzi8ylz3mn0flm2-wlroots-0.9.1/include -I/nix/store/ddhdz49i8g04dln2kcia2l8gjkkxif7k-libxkbcommon-0.8.4-dev/include -I/nix/store/v5i4jmhg21a76b54w2nallhhyjywl7xk-libinput-1.14.3-dev/include -I/nix/store/k5bfpx5x84lg8bv3chlg0yj74nvrsrwl-pixman-0.38.4/include/pixman-1 -I/nix/store/9b5qa2r4z6sisf2qyrhmnhfb4p85zzkd-libdrm-2.4.100-dev/include -I/nix/store/9b5qa2r4z6sisf2qyrhmnhfb4p85zzkd-libdrm-2.4.100-dev/include/libdrm -I/nix/store/5rpsb3sgjq5b3qip0gb5ymv0nq16b5rg-mesa-19.3.1-dev/include -I/nix/store/6lyzq2a2ymdicbgngwzada7by1xjfn2k-libglvnd-1.2.0-dev/include -I/nix/store/4lgpn6gd73fhnrbvxv4bj124j92k65v4-glm-<IP_ADDRESS>/include -I/nix/store/4r76dpgwgyi65dnzw7pnjad1vmn6zkih-wf-config-0.3/include/wayfire -I/nix/store/fh7x6jlyjp6kad0bakwsffdqzng4wmkq-libjpeg-turbo-2.0.3-dev/include -I/nix/store/72mklszjlpy55iiici6waz69dm5sphgf-zlib-1.2.11-dev/include -I/nix/store/daykmk7a0r0qcm2g1y24asgzckl9hz67-libpng-apng-1.6.37-dev/include/libpng16 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c++14 -DWLR_USE_UNSTABLE -Wno-unused-parameter -MD -MQ 'src/25a6634<EMAIL_ADDRESS>-MF 'src/25a6634<EMAIL_ADDRESS>-o 'src/25a6634<EMAIL_ADDRESS>-c ../src/view/layer-shell.cpp
../src/view/layer-shell.cpp: In member function 'void wf_layer_shell_manager::handle_map(wayfire_layer_shell_view*)':
../src/view/layer-shell.cpp:94:32: error: 'struct wlr_layer_surface_v1' has no member named 'layer'
   94 |         layers[view->lsurface->layer].push_back(view);
      |                                ^~~~~
../src/view/layer-shell.cpp: In member function 'void wf_layer_shell_manager::handle_unmap(wayfire_layer_shell_view*)':
../src/view/layer-shell.cpp:102:45: error: 'struct wlr_layer_surface_v1' has no member named 'layer'
  102 |         auto& cont = layers[view->lsurface->layer];
      |                                             ^~~~~
../src/view/layer-shell.cpp: In member function 'wf::layer_t wayfire_layer_shell_view::get_layer()':
../src/view/layer-shell.cpp:342:23: error: 'struct wlr_layer_surface_v1' has no member named 'layer'
  342 |     switch (lsurface->layer)
      |                       ^~~~~
../src/view/layer-shell.cpp:358:1: warning: control reaches end of non-void function [-Wreturn-type]
  358 | }
      | ^
ninja: build stopped: subcommand failed.

However there is already a new upstream release (0.3.1) that should address this: "Compatible with wlroots 0.9.X, wf-shell 0.3 and wf-config 0.3.".
The easiest solution would probably be to update this PR to 0.3.1 and merge it after https://github.com/NixOS/nixpkgs/pull/76787 (i.e. after the final release of Sway 1.3).

What's the ticket here? Current release of wayfire should be compatible with the current version of wlroots in nixpkgs.

Closed in favour of #86606 or #86569


encoding/protojson: add custom marshall/unmarshall support

This PR adds a configuration parameter to both MarshalOptions and UnmarshalOptions that allows the user to define custom encoding/decoding functions for specific message types.
My specific use case of this functionality is to support encoding and decoding of some of the most accepted date types (i.e. https://godoc.org/cloud.google.com/go/civil and https://github.com/googleapis/googleapis/blob/master/google/type/date.proto) into the ISO 8601 format for those types.  Adding to the "well known types" is not an option as the types are not actually well known types.  This also adds flexibility to allow multiple Json values to represent the same deserialized data. (i.e. in this example, the date could be specified as an ISO 8601 string or as an object with a "year", "month" and "day" fields).
Because this relies on the functionality in "internal/encoding/json" package, I have exposed the Kind type and multiple interfaces in the "protojson" package that correspond to the types defined in the internal package.
This should provide sufficient flexibility in implementations.

Thanks for the PR, but this project does not use GitHub pull requests, but Gerrit. See the contributor guide: https://github.com/protocolbuffers/protobuf-go/blob/master/CONTRIBUTING.md
That said, this is a major API change and needs to be discussed. Please file open an issue https://github.com/golang/protobuf/issues

Apologies!  Should have read more :-) I've created https://github.com/golang/protobuf/issues/1098 and created a Gerrit review for the changes I've made. I'll close the PR In favor of those.


PSO doesn't return solutions in order

Solutions returned from particle swarm optimiser are not in order of quality.

#5 just needs a commit adding something like
return sorted([ p.as_sol() for p in pop ], key=lambda p: p.fitness)

#5 just needs a commit adding something like
return sorted([ p.as_sol() for p in pop ], key=lambda p: p.fitness)

Closed with 4946aec

Closed with 4946aec


support dynamic metrics collection in endpoint operator

fixe: https://github.com/stolostron/backlog/issues/20601
Signed-off-by: Marco<EMAIL_ADDRESS>

/retest


Upgrade to snappy 1.1.9

Snappy 1.1.9 was released on 2021-05-05 (a year ago).
Would you be so kind and let us know when you plan to update snappy-java?

+1

+1

Released https://github.com/xerial/snappy-java/releases/tag/v<IP_ADDRESS>


Update SiteGoF.R

Transitioned code to using dplyr
Fixed bug related to monthly results

I am onboard with transitioning to dplyr, but I do not know off-hand how many functions rely on plyr. If it is a small effort to transition all functions to dplyr that currently use plyr then I will move forward with that.
I will review the bug fix. Could you elaborate on what bug your change fixes?
Thanks for the contribution and I'll take a closer look in the morning

Sorry! I didn't mean to jump the gun on transitioning to dplyr.
The original SiteGoF function was returning NAs for the monthly goodness-of-fit statistics calculated for the January to September (e.g. the documented example should return all 0s and 1s).


Crash on adding Host Pathogen Annotation

Found the exact line causing the crash.

Output with print statements:

Specifically, passing the parameter "wd_item_id=..." causes it to become unresponsive. Tried setting a hard value like so:
wd_item_protein = wdi_core.WDItemEngine(wd_item_id='Q21168345')
But it also crashed the server
@putmantime @andrewsu Thoughts?

Problem with outdated wdi. Going to update it now.

HP now works, going to check with other annotations.

@khybiske when you get a chance, can you try resubmitting the annotation in the host pathogen interactions module? I believe it is fixed...

@djow2019 I just submitted one for CTL0260 and it said I was successful. Let's see if it updates.


There is no usable working Builder for a FunctionCallback

Bug description
The class DefaultFunctionCallbackBuilder has a field private String inputTypeSchema, but there is no .build() method to costruct an instance of a FunctionCallback defined at runtime. The class FunctionInvokingFunctionCallback has not public constructor.
Environment
Spring AI version: 1.0.0-SNAPSHOT
Java version: 17
Expected behavior
I need a public usable Builder where I can set the name, the description and the JSON schema in string format (and not necessarily a Class) and returning an instance of FunctionCallback.
	DefaultFunctionCallbackBuilder defaultFunctionCallbackBuilder = new DefaultFunctionCallbackBuilder();
	FunctionCallback.Builder builder = defaultFunctionCallbackBuilder
			.description(description).inputTypeSchema(parameters)
			.schemaType(FunctionCallbackContext.SchemaType.JSON_SCHEMA);
	FunctionCallback functionCallback = builder.build();    // MISSING !
	ChatOptions promptOptions = AzureOpenAiChatOptions.builder()
			.withResponseFormat(AzureOpenAiResponseFormat.JSON)
			.withFunctionCallbacks(List.of(functionCallback)).build();

Some changes were made to the builder since we got to triage this issue.
You can use this style of the builder to achieve what you want now.
	FunctionCallback.builder().function("functionName", input -> "output").inputTypeSchema("my custom schema").description("my description").schemaType(FunctionCallback.SchemaType.JSON_SCHEMA);

Let us know if this solves your issue.
Thanks


Request Outline Capability In Combination With PowerShell Classes

PowerShell development for scripts that do NOT utilize classes can be parsed by VS Code in such a way that allows for VS Code to properly outline each PowerShell function. You can see this under the VS Code Explorer (Ctrl + Shift + E), there is an "OUTLINE" section. However, when building PowerShell classes the outlining capability doesn't appear to be introduced as of VS Cpde 1.72.2.  I would like to request that PowerShell support outlines for PowerShell classes.
I wasn't able to locate an existing feature request for this, which is surprising because I've seen this issue asked for on StackOverflow. so I have to believe I just missed it in the backlog somewhere. Additionally, I've not found a suitable extension for this either.

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!

Can you explain why the feature is partially implemented

No, I can't. What I meant to say that this is the wrong repo and that you need to reach out to the powershell extension, not VS Code itself

Understood, and thank you for that. So, you confirm that the outlining capabilities related to PowerShell functions (not classes) aren't implemented by VS Code, it must be from an extension I have installed somewhere? I have a few extensions installed, so maybe I mistook that it was baked directly into VS Code.


feat: Move backoff to to the tracker to remove errors

fixes #318

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

9 of 26 (34.62%)  changed or added relevant lines in 2 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 70.302%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tap-agent/src/agent/sender_fee_tracker.rs
7
24
29.17%

Files with Coverage Reduction
New Missed Lines
%

tap-agent/src/agent/sender_account.rs
3
92.64%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.2%

Covered Lines:
4486

Relevant Lines:
6381

💛  - Coveralls

@carlosvdr The main thing looks good to me but I'm going to let @gusinacio take a look 👍


Bug:  If there’re more, then 6 Figma frames in 1 row - name of the frame doesn’t fit

Issue
If there’re more, then 6 Figma frames in 1 row - name of the frame doesn’t fit
Scenario
Issue can be reproduced following this exact scenario below:

Go to https://cloud.supernova.io/
Go to Docs
Add more then 6 Figma frame blocks in 1 row
Publish
View

Expected result
As a user I expect, that the names at Figma block will be displayed properly, no matter how many of them in 1 row.
Additional information

Versions used

Documentation Exporter version 4.0.0 (Nebula)
OS: macOS Monterey 12.4 (21F79).

Resolved in ENG-401


adding Efficient V2 XL

Hi,
thanks for the info. I didn't realize they released XL variant.
I did some quick prototyping yesterday and there are few issues. The XL model is so big that it:

crashes the layer naming convention
upon being created throws python RecursionError - my guess, due to the number of layers.

I will be trying to add it, but I do not have much time now, so it might take a while from my side.
Thanks.

You can take your time no problem

I'm closing this as XL has been added. Feel free to repoen if you have questions.


A bug like the follow picture

made by:remove all project folder in tree-view,then close the pane to close all opened file
i can't duplicate the bug
os win10x64 atom v1.3

Please let us know if you can get any more information. Also please try to reproduce this using Safe Mode:
To launch Safe Mode:

Completely exit all instances of Atom
Launch Atom with the command atom --safe

Thank you for your issue!
We haven't gotten a response to our questions in our comment https://github.com/atom/atom/issues/10011#issuecomment-163856211. With only the information that is currently in the issue, we don't have enough information to take action. I'm going to close this but don't hesitate to reach out if you have or find the answers we need, we'll be happy to reopen the issue.


It doesn't work

Expected Behaviour
it works
Current Behaviour
your doco is wrong, and it doesn't work. fix it you Billion $ company!

Code snippet
yeah nah

Possible Solution
No response
Steps to Reproduce
fix is

Thank you for opening this issue and bringing it to our attention. We have addressed the problem and it has now been fixed. If you encounter any further issues or have any additional questions, please don't hesitate to let us know.

Nope not fixed. look at your doco. look at npm.
go through your cdk steps in detal. sjc


Single source of truth for open stations and current lines

A station being open or a line being current has two sources of truth in them. I though this might make maintenance just a little easier by providing a single source of truth for those two properties.

Great idea. Maintainability is what all of this latest version is about.


[BUG] [CCI] Running yo-doc and yo-component scripts crashes with an error

Describe the bug
Running yo-doc and yo-component scripts crashes with the following error
$ yo ./generator-oui/app/documentation.js
internal/modules/cjs/loader.js:1131
      throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
      ^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /Users/andreymyssak/Gomasko/Projects/opensearch/oui/node_modules/trim-newlines/index.js
require() of ES modules is not supported.
require() of /Users/andreymyssak/Gomasko/Projects/opensearch/oui/node_modules/trim-newlines/index.js from /Users/andreymyssak/Gomasko/Projects/opensearch/oui/node_modules/meow/index.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename /Users/andreymyssak/Gomasko/Projects/opensearch/oui/node_modules/trim-newlines/index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /Users/andreymyssak/Gomasko/Projects/opensearch/oui/node_modules/trim-newlines/package.json.

    at new NodeError (internal/errors.js:322:7)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1131:13)
    at Module.load (internal/modules/cjs/loader.js:979:32)
    at Function.Module._load (internal/modules/cjs/loader.js:819:12)
    at Module.require (internal/modules/cjs/loader.js:1003:19)
    at require (internal/modules/cjs/helpers.js:107:18)
    at Object.<anonymous> (/Users/andreymyssak/Gomasko/Projects/opensearch/oui/node_modules/meow/index.js:8:20)
    at Module._compile (internal/modules/cjs/loader.js:1114:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)
    at Module.load (internal/modules/cjs/loader.js:979:32) {
  code: 'ERR_REQUIRE_ESM'
}
error Command failed with exit code 1.

To Reproduce
Steps to reproduce the behavior:

Open project
Run yarn yo-doc or yarn yo-component
See the error

Expected behavior
Generation of files according to scripts
Host/Environment (please complete the following information):

OS: macOS Ventura v13.2
Node v14.21.3
Yarn v1.22.19

PR has been merged into main :+1:


if i only have destination ip, can i proxy it?

i mean i dont have its domian so i cant add to the domain list, only have ipv4 address, can i proxy it?

unfortunately not. as the name suggests, sniproxy works on sni which is a TLS extension when the connection has a domain (FQDN in fact).


Uncaught Error: Cannot find module 'atom-message-panel'

I use the latest atom version (0.120.0) and I have installed Linter and Flake8 on my system.
My OS is MacOS X

Closing as reporter didn't provide more detailed feedback.


parentage check: phospholipid translocation

phopholipid translocation
has the parent
"regulation of membrane lipid distribution"
but isn't  "phopholipid translocation" part of membrane lipid distribution (if that is a process)
It seems that the  process term would be "membrane lipid localization"?

"regulation of membrane lipid distribution"
is an is_a child of regulation of a biological quality - the quality being 'membrane lipid distribution'
and an is_a child of single-organism membrane organization
I think everything is in order.

Yeah, it seems a little odd that this as "regulatory". The translocation is causing the distribution, but not necessarily regulating it? (Unless the flippases actually sense the lipid distribution and regulate accordingly?)

The definition of ROBQ (regulation of biological quality), the parent term:
"Any process that modulates a qualitative or quantitative trait of a biological quality. A biological quality is a measurable attribute of an organism or part of an organism, such as size, mass, shape, color, etc."
In this case, the measurable attribute is 'membrane lipid distribution' and the regulatory process is modulating where the lipids are distributed. In my understanding,  phospholipid translocation is a process that modulates where lipids are distributed within a membrane, therefore it is a 'regulation of membrane lipid distribution'.  Note the existence of a second is_a parent, single-organism membrane organization, which also adds information to this term.

ok,


Jurassic World Evolution

It just keeps on crashing when i put the files into the folder of Jurassic World Evolution so i really dont know what to do with that.

GitHub issues is not meant for user support. Head on to the forum, search and ask around there.

GitHub issues is not meant for user support. Head on to the forum, search and ask around there.


in about us section text is not appearing and there is hover effect

Describe the feature
In the footer section of the About US, the text of the quick link does not appearing the text hovering is not good
Add ScreenShots

please assign me @pa
please label it under gssoc and level
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Assigned!
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it. Happy open-source contributing!


maestral-qt: set mainProgram and changelog meta attributes

Description of changes
As per title.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Already did that in https://github.com/NixOS/nixpkgs/pull/202744, I just put this one in a separate PR because it also 'fixes' something (nix run nixpkgs#maestral-gui).


Signs

What version of ViaVersion are you using? Type /ver viaversion
0.7.9
What version of Spigot are you using? Type /ver
1.8.8
What plugins are you using? Type /plugins

Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
No bungee
Newest of all plugins
How does this error happen? login? Using an item?
Randomly some signs dont workd
Is there an error in the console? Use pastebin.com. Is there a kick message?
Nope

Duplicate of #352

MVDWPLACEHOLDERS is not used, so this is not really a duplicate i think!
This happens randomly with every sing on 1.9.

Also happens with ProtocolLib, title was wrong.


fix: add Cargo.lock

[ ] Tested on all platforms changed
[ ] Compilation warnings were addressed
[ ] cargo fmt has been run on this branch
[ ] cargo doc builds successfully
[ ] Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
[ ] Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior
[ ] Created or updated an example program if it would help users understand this functionality
[ ] Updated feature matrix, if new features were added or implemented

None of the former fulfilled as this was done to address doukutsu-rs/doukutsu-rs#273

maybe it's worth bringing up upstream? https://github.com/rust-windowing/winit


Main > Live

Docs Build status updates of commit 7c20910:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TerminalDocs/tutorials/custom-prompt-setup.md
:warning:Warning
View
Details

TerminalDocs/command-line-arguments.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/actions.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/interaction.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-advanced.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-appearance.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-general.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/startup.md
:white_check_mark:Succeeded
View

TerminalDocs/faq.yml
:white_check_mark:Succeeded
View

TerminalDocs/index.md
:white_check_mark:Succeeded
View

TerminalDocs/json-fragment-extensions.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/new-tab-same-directory.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/custom-prompt-setup.md

Line 43, Column 123: [Warning: file-not-found - See documentation] Invalid file link: 'windows/package-manager/winget'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 269670c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TerminalDocs/tutorials/custom-prompt-setup.md
:warning:Warning
View
Details

TerminalDocs/command-line-arguments.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/actions.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/interaction.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-advanced.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-appearance.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-general.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/startup.md
:white_check_mark:Succeeded
View

TerminalDocs/faq.yml
:white_check_mark:Succeeded
View

TerminalDocs/index.md
:white_check_mark:Succeeded
View

TerminalDocs/json-fragment-extensions.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/new-tab-same-directory.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/custom-prompt-setup.md

Line 43, Column 123: [Warning: file-not-found - See documentation] Invalid file link: './package-manager/winget'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit dfe55d0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TerminalDocs/tutorials/custom-prompt-setup.md
:warning:Warning
View
Details

TerminalDocs/command-line-arguments.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/actions.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/interaction.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-advanced.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-appearance.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-general.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/startup.md
:white_check_mark:Succeeded
View

TerminalDocs/faq.yml
:white_check_mark:Succeeded
View

TerminalDocs/index.md
:white_check_mark:Succeeded
View

TerminalDocs/json-fragment-extensions.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/new-tab-same-directory.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/custom-prompt-setup.md

Line 43, Column 123: [Warning: file-not-found - See documentation] Invalid file link: './../package-manager/winget'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a7a0eca:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TerminalDocs/tutorials/custom-prompt-setup.md
:warning:Warning
View
Details

TerminalDocs/command-line-arguments.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/actions.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/interaction.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-advanced.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-appearance.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-general.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/startup.md
:white_check_mark:Succeeded
View

TerminalDocs/faq.yml
:white_check_mark:Succeeded
View

TerminalDocs/index.md
:white_check_mark:Succeeded
View

TerminalDocs/json-fragment-extensions.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/new-tab-same-directory.md
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/custom-prompt-setup.md

Line 43, Column 123: [Warning: file-not-found - See documentation] Invalid file link: '../../package-manager/winget'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Use linear memory when creating token contract

Blocked by https://github.com/stellar/rs-stellar-contract-sdk/issues/247

Instead of doing that here, we should just make Binary use linear memory under the hood. It shouldn't be something, I think, that the contract has to make a cognitive decision about. If I'm misunderstanding what this issue is, can you elaborate?

I 100% agree. This issue was opened before array/slice to Binary conversions were even available, so it was actually looping over the WASM byte-by-byte. Now that it uses the existing conversions functions, it should happen seamlessly when we do https://github.com/stellar/rs-soroban-sdk/issues/247.


Upgrade rn-builder-bob to enable tree-shaking in rn-web

Summary
The .web.js path in this library currently breaks tree-shaking in web projects, causing them to import the entire ~250kb of react-native-web regardless of their other configuration:

This is because the module build artifacts like lib/module/ReactNativeSVG.web.js are in pure ES5 and not ES5+ESM (es5 but preserving import/export statements).

Updating to the latest version of rn-builder-bob (which had a prerequisite fix in https://github.com/callstack/react-native-builder-bob/pull/363 for this library) fixes this, generating the proper ES5+ESM output for the module build (while leaving the commonjs build in pure ES5 with require):

Test Plan
This change should only affect the build output and not anything in the native layers.
Verified against simulators:

What's required for testing (prerequisites)?
n/a
What are the steps to reproduce (after prerequisites)?
Generally navigate around and see that everything still works.
Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[x] (n/a) I added documentation in README.md
[x] (n/a) I updated the typed files (typescript)
[x] (n/a) I added a test for the API in the __tests__ folder

Looked into the failing builds and realized I'd pulled from our private registry at first. Regenerated yarn.lock changes from public registry.

@merrywhether Could you also bump the version of node used in the JS build workflow? Based on the failed build it should be 16 here:
https://github.com/software-mansion/react-native-svg/blob/d6975ea9f20f2fefb603f2612fdb3bbc7bf071ca/.github/workflows/js-build-test.yml#L21
and it the step name.
Ok I edited the PR and all checks pass now 🚀

Thanks for bumping that. Sorry I was a little slow on the follow-up responsiveness here but happy that we got it merged.

Yeah no problem 😅


Topics (Listen) supported

old param detect_topics should be kept for backwards compatibility cases.
new param topics added for topic detection for /listen requests.

PR Merged. Will be available on the next release (hopefully today).


Examples using findDOMNode()

Using findDOMNode() is no longer recommended. In fact, if you use it, React will warn you not to. Some of the examples use findDOMNode in places where I don't think you can use refs to replace them. These should be updated to use something else if we shouldn't be using findDOMNode anymore.
One specific example of this is here: https://github.com/gaearon/react-dnd/blob/master/examples/04 Sortable/Simple/Card.js#L34
const cardTarget = {
  hover(props, monitor, component) {
    const dragIndex = monitor.getItem().index;
    const hoverIndex = props.index;

    // Don't replace items with themselves
    if (dragIndex === hoverIndex) {
      return;
    }

    // Determine rectangle on screen
    const hoverBoundingRect = findDOMNode(component).getBoundingClientRect();

    // Get vertical middle
    const hoverMiddleY = (hoverBoundingRect.bottom - hoverBoundingRect.top) / 2;

    // Determine mouse position
    const clientOffset = monitor.getClientOffset();

    // Get pixels to the top
    const hoverClientY = clientOffset.y - hoverBoundingRect.top;

    // Only perform the move when the mouse has crossed half of the items height
    // When dragging downwards, only move when the cursor is below 50%
    // When dragging upwards, only move when the cursor is above 50%

    // Dragging downwards
    if (dragIndex < hoverIndex && hoverClientY < hoverMiddleY) {
      return;
    }

    // Dragging upwards
    if (dragIndex > hoverIndex && hoverClientY > hoverMiddleY) {
      return;
    }

    // Time to actually perform the action
    props.moveCard(dragIndex, hoverIndex);

    // Note: we're mutating the monitor item here!
    // Generally it's better to avoid mutations,
    // but it's good here for the sake of performance
    // to avoid expensive index searches.
    monitor.getItem().index = hoverIndex;
  }
};

Other examples: https://github.com/gaearon/react-dnd/search?l=JavaScript&q=finddomnode&utf8=✓
What is the recommended way to resolve this?

recommended way of doing it is by using refs, see: https://facebook.github.io/react/docs/refs-and-the-dom.html

The way we've fixed it on our end is as follows:
In our draggable:
<li className="draggable-card" ref={(elm) => {this.card = elm;}}>

And inside of our DropTarget hover method.
hover (props, monitor, component) {
     // code
    const {decoratedComponentInstance} = component;
    const hoverBoundingRect = decoratedComponentInstance.card.getBoundingClientRect();
    // code
}

I'm not sure if there are better ways to go about this, maybe @gaearon can shine some light on this. That would be greatly appreciated.

That's the recommended way from facebook docs. We are doing it in the same fashion

If I have some time I'll look at this later. In the meantime feel free to cut a PR

We're taking the ref approach, but component.decoratedComponentInstance is null.
Just for reference, our components are both draggable & droppable:
export default flow(
  DragSource('NavItem', navItemDragSource, dragCollect),
  DropTarget('NavItem', navItemDropSource, dropCollect)
)(NavigationItem);

Our NavigationItem component sets the ref we expect to use in hover:
class NavigationItem extends React.Component
  render() {
    return this.props.connectDropTarget(this.props.connectDragSource(
      <section
        ref={element => (this.navItemElement = element)}
     </section>
  }
}

And in hover:
const navItemDropSource = {
  hover: (props, monitor, component) => {
    console.log(component.decoratedComponentInstance); // prints null
  }
}

Any idea what we're missing here?

In our app it looks roughly like that:
..some code

const itemTarget = {
  hover(props, monitor, component) {
    if (monitor.isOver()) {
      ...some code

       const bounds = component.node.getBoundingClientRect()

       ...some code
       return result;
    }
  }
}

..some code

@DragSource(ITEM_TYPE, itemSource, collectSource)
@DropTarget(ITEM_TYPE, itemTarget, collectDrop)

class DraggableItem extends Component {
  render() {
    const { connectDragSource, connectDropTarget } = this.props;

    return connectDragSource(
      connectDropTarget(
        <div
          className="draggable-item"
          ref={ node => (this.node = node) }
        >
          <Item { ...this.props } />
        </div>
      )
    );
  }
}

export default DraggableItem

in your example I see that you are assigning the element param to this.naItemElement but in hover method you are not referring to naItemElement at all. You should call it something like that:
const navItemDropSource = {
  hover: (props, monitor, component) => {
    console.log(component.navItemElement); // you should get the DOM node reference now
  }
}

Got is working! It turns out the trick was to call connectDropTarget first. I don't think connectDragSource sets decoratedComponentInstance.
Our working version looks like this:
class NavigationItem extends React.Component
  render() {
    return this.props.connectDragSource(this.props.connectDropTarget(
      <section
        ref={node => (this.node = node)}
      >
       {this.props.name}
      </section>
    ));
  }
}

const navItemDropSource = {
  hover: (props, monitor, component) => {
    console.log(component.decoratedComponentInstance.node.getBoundingClientRect());
  }
}

I am glad I am not the only one worried about this feature being deprecated. I am currently using a 3rd party 'Webcam' component found here https://github.com/mozmorris/react-webcam. This component uses findDOMNode and I do not see how refs can be used to replace the functionality.
Here is the simple example of how you can use this component.
class WebcamCapture extends React.Component {
setRef = (webcam) => {
this.webcam = webcam;
}
capture = () => {
const imageSrc = this.webcam.getScreenshot();
};
render() {
return (

Capture photo

);
}
}
I think if you wanted to change this to do refs than the example code would require the user of this 3rd party library to understand the dom structure of the Webcam component which is using a  dom element and the getusermedia API which is not ideal to say the least. Please let me know if I am missing a simpler way to do this using refs.

I need to add some pins over an image and to get the drop component's viewport positions, I added the ref node like @QuentinRoy suggested but the getDecoratedComponentInstance() didn't work for me (is not a function :-).
I saw that I can get the node reference directly on the component param in the drop method of the drop target spec:
drop: (props, monitor, component) => {
   console.log(component.node.current.getBoundingClientRect())
}


Update Network to Anycast

Please upgrade network to Anycast for highest accuracy in determining user’s geolocation.
Anycast is a method for addressing and routing. In this method, the same IP address is allocated to a group of server nodes which, within a CDN framework, act as a series of servers in different datacenters throughout the world. The traffic sent to this IP address is responded by the topologically closest server to the transmitter of the request. As a result, ArvanCloud IP addresses are simultaneously advertised worldwide, and every user can connect to the closest edge server and get services through the first connection.

There is no technical limitation in this software to not use anycast.


Eileen

Changes to str formating for writing photometry and publication_id to publication_shortname

Won't merge this into master. Sorry Eileen! This version has diverged so much from master that I think most of these commits are moot and we would need to reevaluate any others.


Support ignore-sripts

what are the ignore-scripts?

From https://github.com/npm/npm/blob/master/doc/cli/npm-install.md

The --ignore-scripts argument will cause npm to not execute any scripts defined in the package.json. See npm-scripts(7).

Thanks! That's reasonable.

still need to add it to --help though


Dealing with violations is necessary

I know cargo-vet deliberately avoids having overrides for violation, but this causes problems that make adoption of cargo-vet difficult.
Lack of conditional audits
For example, the hostname crate has a memory-safety bug, but only on Windows, and only if the set feature is used. There is a real safety violation there, but Linux projects or projects not using set are not affected.
cargo-vet doesn't have per-platform, per-feature, per-function audits, so I can't express the real safety situation of this crate. I have a choice of making a technically false audit saying the crate is safe, or audit it as a violation, and cause a headache for projects that are not affected.
I don't think custom criteria help here. I can't switch to using something like safe-to-deploy-only-on-linux, because safe-to-deploy is a built-in criterion, and I can't add implies to it.
Distributed audits are at odds with coordinated audits
The second problem is that audit conflicts are fatal errors. cargo-vet says to just talk to the audit author, but if I use audits from the registry, I'd need to chase people from external companies.
This is highly problematic when I use cargo vet in my CI as a blocking check. I really want to reuse other people's audits, because otherwise auditing is too much work. But I can't be dependent on someone else, in another company, in another timezone, updating their audit for me. They may not even agree to change their audit, since there can be contentious cases like the aforementioned hostname crate.

So I really miss having a feature to say "I've reviewed this audit/violation, and I think it's OK to ignore it for this project". As a precaution, it could have an expiry date to force a periodic re-review of such overrides.

Our story around violations is unfortunately one of the weaker ones in cargo-vet, just due to the use-cases being less developed due to relatively infrequent use. I can definitely see us wanting to add something more in this area in the future.
That being said it is currently possible for you to locally resolve a dispute like this one from within your own supply chain by adding the crate in question to the violation source's exclude list in your config.toml (https://mozilla.github.io/cargo-vet/config.html#exclude) - this will prevent all audits and violations for the crate from being imported from that source.


Object type not assignable to equivalent value of mapped type

Code
// Pack<{ a: number }> is { a: { value: number } }
type Pack<T> = { [K in keyof T]: { value: T[K] } };

function patch<T, K extends keyof T>(obj: Partial<Pack<T>>, key: K, value: T[K]) {
    obj[key] = { value }; // error: Type '{ value: T[K]; }' is not assignable to type 'Pack<T>[K]'.
}

Example usage of patch():
type SomeType = {
  a: number, b: string
};

const obj: Partial<Pack<SomeType>> = {
    a: { value: 1 }
}

patch(obj, 'b', 'foo'); // desired outcome is for obj.b to equal 'foo'

Expected behavior:
Definition of patch() function should be fine, and calling should produce the desired outcome.
Actual behavior:
patch() function fails to compile with error Type '{ value: T[K]; }' is not assignable to type 'Pack<T>[K]' even though { value: T[K] } does appear to be assignable to Pack<T>[K]:
function getPack<T, K extends keyof T>(obj: T, key: K): Pack<T>[K]  {
    const value = obj[key]; // T[K]
    return { value }; // { value: T[K]; }
}

Playground Link:
Additional examples here: https://bit.ly/2le5qZq

@DanielRosenwasser I'm not sure I totally understand. So then why does Pack<T> (rather than Partial<Pack<T>>) work as expected? What's an example of a situation where the expected behavior I outlined above would be incorrect?

Okay, a couple of things:
First, this works the way you want under strictNullChecks which is odd. I don't know why that is off the bat.
Second, really neither should work. Seems like actually that's the bug.
Third,

What's an example of a situation where the expected behavior I outlined above would be incorrect?

interface Container<T> { value: T };
type Pack<T> = { [K in keyof T]: Container<T[K]> }

function patch<T, K extends keyof T>(obj: Partial<Pack<T>>, key: K, value: T[K]) {
    obj[key] = { value };
}

let boxCollection = {
    foo: {
        value: 100,
        shapeType: "cube",
    },
    bar: {
        value: 200,
        shapeType: "sphere",
    }
};

patch(boxCollection, "foo", 100);

// Crash!
boxCollection.foo.shapeType.toLowerCase();

Thanks for the example - very helpful. If I understand correctly, the issue is that you can't just blindly assign something to obj[key] because the type of obj[key] may be more derived than Box<T>. Not to muddy the waters, then, but shouldn't the following work just fine?
function patch<T, K extends keyof T>(obj: Partial<Pack<T>>, key: K, value: T[K]) {
    obj[key].value = value; // Error: Property 'value' does not exist on type 'Partial<Pack<T>>[K]'.
}

@DanielRosenwasser any ideas here?

Closing as the original example is no longer an error.


Merge python3 and changes for hysds/isce2 into develop branch

Changes EOS made for hysds3 core :

Merged python3into develop
Fixes to docker/Dockerfile

use hysds3 compliant image hysds/isce2
No need for pip3 since base image uses python3
fix issue in the new hysds/isce2 base image where mpl_toolkit.basemap could not find boundary files (see below)

In initiate_standard_product_enumurator.sh : Use verdi's python3 instead of root's
In docker/setup.sh: Use ariamh's python3 branch which uses updated isce.sh for environment variables inhysds/isce2
In standard_product_localizer.py: Update standard_product_localizer to use consistent spacing for indentation

All the logs of succesful standard_product running on hysds3:
Enumerator job complete logs
Localizer job complete logs
Ifccfg evaluator job complete logs

^ accidentally deleted branch, sorry!

@mkarim2017  Ready for review


Added accessibility for constrained badges

Platforms Impacted

[X] iOS
[ ] macOS

Description of changes
Voice over doesn't work for constrained badges.
'+5' button is not accessible through the swipe gesture and while navigating using right swipe screen reader does convey the information about the hidden element.
Link to work item is here.
Repro Steps:
Step 1: Open FluentUI application.
Step 2: Navigate to 'BadgeField' button using swipe gesture.
Step 3: Navigate to '+4' button and observe the issue.
Fix:
Handle constrained badges accessibility elements by reading values from appropriate elements array.
Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[X] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)

Microsoft Reviewers: Open in CodeFlow

please do not add internal only ado links in pr descriptions

please do not add internal only ado links in pr descriptions

I have removed the link.


More translations

#124

Thank you so much for translating to Russian!! Thanks also for catching all of those typos.
I noticed that just a few of the strings were left untranslated. Would it be possible for you to translate these too?

ipThrottling_invalid
option_cacheControl_description
option_excludeDotHtml_description
option_spa_description
remove_plugin_confirm_description
add_plugin_failed_description
setting_plugins_description
setting_tray_description

I think they're important. Would you be able to translate them? If not, I'll just use Google Translate.

@terreng done, pls merge

@terreng I added the missing translation and added README_ru.md.
Here is the text that you asked to translate
Создавайте локальный веб-сервер в несколько кликов с помощью простого интерфейса.

Простота настройки
Настройки сервера можно менять под себя в несколько кликов.

Множество веб-серверов в фоновом режиме
Запускайте несколько веб-серверов одновременно, даже когда приложение закрыто.

Одностраничные приложения
Легко можно включить перенаправление запросов для одностраничных приложений Single Page Applications (SPA).

@stokito Thank you for your contribution! We just released version 1.2.7 which adds Russian. The update is available now on our website and will be available from the Mac App Store and Microsoft Store soon. Thanks again!

Thank you, on the website left some untranslated text:

Download: Скачать
Documentation: Документация
Made with ❤ by @terreng and @ethanaobrien: Сделано с любовью авторами @terreng и @ethanaobrien.
A continuation of Web Server for Chrome by @kzahel.: Это продолжение почившего Web Server for Chrome от @kzahel
Chinese translations by @antnesswcm.: Перевёл на китайский @antnesswcm

I don't feel like my name is needed to be added for the Russian translation.

Thanks for providing those translations!

I don't feel like my name is needed to be added for the Russian translation.

Would you like me to remove the credit from the website?

no I just mean that it makes no sense to add a similar text "Russian translation by stokito". It's anyway can be seen on github and many others may contribute so it will be outdated.

Would you like to be credited on the website or not?

no

Thanks for clarifying. I'll remove it.


Username and password authentication + JWT

For a starter authentication scheme, implement username and password authentication which returns a JWT token.

forgot to backlink https://github.com/massivebugs/home-feature-server/pull/2


proposal: Go 2: add untyped() type conversion for integer constants

Proposal
This proposal extends the late-type-binding aspect of untyped constants to situations where the construction of a constant caused a type to be set, but the result is best used/considered as an untyped constant.
Background
There is a gentle robustness to untyped constants. I can add a plain "3" to any numeric expression without casts and verbosity. I want that for derived constants as well and offer the rationalization that even where typed constants are important in a computation, as in ^uint16(0), the result may not itself be usefully typed—the 65535 that results is just the integer 65535, so why should I not be able to add it to an int or uint loop index? untyped(expr) solves this.
Example
Here is an example from a few days ago using the present state:
import (
	"unsafe"
)

//1, 2, 4, 8
const wordBytes = int(unsafe.Sizeof(uintptr(0)))

// 0, 1, 2, 3
const logWordBytes = 0 +
	3*((wordBytes>>3)&1) + // 64-bit machine aligns 0 of 0..7
	2*((wordBytes>>2)&1) + // 32-bit machine aligns 0 of 0..3
	1*((wordBytes>>1)&1) + // 16-bit machine aligns 0 of 0..1
	0 //  8-bit machine always aligns

// 0, 0b1, 0b11, 0b111
const alignMask = uintptr(wordBytes - 1) // == (1<<logWordBytes)-1

Neither the int in int(unsafe.Sizeof(uintptr(0))) nor the uintptr in uintptr(wordBytes - 1) were what I wanted; I wanted a plain untyped integer. (As Rob asked in a video, "What was wrong with the old integer 80?") It was just that the expressions garnered a type and I could not "un-type" them.
I would like to see this instead:
import (
	"unsafe"
)

//1, 2, 4, 8
const wordBytes = untyped(unsafe.Sizeof(uintptr(0)))

// 0, 1, 2, 3
const logWordBytes = 0 +
	3*((wordBytes>>3)&1) + // 64-bit machine aligns 0 of 0..7
	2*((wordBytes>>2)&1) + // 32-bit machine aligns 0 of 0..3
	1*((wordBytes>>1)&1) + // 16-bit machine aligns 0 of 0..1
	0 //  8-bit machine always aligns

// 0b0, 0b1, 0b11, 0b111
const alignMask = wordBytes - 1 // == (1<<logWordBytes)-1

...which would have given me 8, 3, and 7 as simple constants for further convenient use.
Compatibility
This does introduce a new symbol so it is not impossible that it would be seen as violating the Go1 promise.
Jan Mercl pointed out that users can create a type of their own nameduntyped() as shown here in the Go Playground, so that makes it a guarantee breaking change.
Ian lance Taylor commented that it may be seen in as non-breaking under the notion that "If we treat untyped as an ordinary predeclared identifier, then I think the proposal remains backward compatible.  The new predeclared untyped is not available in packages that defined the name untyped in package scope.  And there is no other way write untyped(EXPR)."
In any case it is a localized change in that it is no change unless a user's created a type named "untyped" and if they have, the compiler and go vet (and go fix) will know and can respond as appropriate, one version of which is to use the user's type cast and then therefore it is not a change in the contract sense but admittedly becomes a potential source of confusion in that hypothetical case.
Ambiguities
This proposal originally focused on integer constants. But discussion here has made clear that it is just as useful generally so that utility and the appeal of orthogonality say that untyped() could remove the float128 from a complex constant just as beneficially.
Implementation
Simple change in the semantic actions of the parser to drop whatever type has been set on a constant.

Thanks.  This leads to the obvious question of how to handle float, complex, rune, string, and bool constants.  These constants too can be both untyped and have a type.  Should untyped work for them as well?  For example, if untyped is given a value of type float32 or float64, should it return a value of untyped float?

You can't normally call a function in a constant instantiation, for obvious reasons. Apparently the unsafe pseudo-package is an exception to this since they're compile-time operations that, as their documentation says, return constants. I didn't realize before that this meant that they could be used like that, though.
The problem you're trying to address seems to stem from the fact that they're returning typed constants. Maybe it would make more sense for them to return untyped constants directly, rather than adding a new pseudo-conversion that would only probably really be used in conjunction with them. Alternatively, make this an unsafe package operation, too. unsafe.Untype(), for example.

[responding to Ian]
The notion of untyped(expr) should be universal if that makes sense parse-wise. Had not really considered what an untyped(complex) would be other than complex, but now I realize from your comment that it would be float64 or float128 tagging that would be removed. Yes, I would change the proposal to make it general.
[responding to DeedleFake]
Indeed although each part of this deserves careful comment:

Neither untyped() nor sizeof() nor hypothetical peers like typeOf(), offsetOf(), minValueOf() are function calls. They are fixed attributes of the argument being exported from the compiler's symbol table.

The general bias against function calls in constant expressions is regrettable. Pure functions should indeed be allowed in such cases. Indeed, consider how much better it would be to initialize a const sqrt2 = math.Sqrt(2) by calling the math function during compilation rather than setting const sqrt2 = 665857.0/470832.0 via a fraction, using an init function and its global variable, through cut-and-paste from Ivy/Mathematica, or hoping that the math package has the special value that you want squirreled away.

That was just an example that came up recently. I'm "sure" emotionally but not recalling hard fact that this has come up before in cases not involving unsafe... Aha! I made one up just now so I do have fact that it is not just about package unsafe, though I still don't remember the previous case:

const h = "hello"
const l = len(h)
const example = byte(5) + l
# xor
./xor.go:26:25: invalid operation: byte(5) + l (mismatched types byte and int)

...and here's an example. the length of "hello" is not the number 5, but rather Go's int(5). Now, why would this be the optimal circumstance? Is it important for static code analysis to halt a developer's "wild" abuse of adding the length of the string to an unsigned variable? Should len() return a number cast to unsigned since it can never be negative and our grandchildren may be >63 bit string cardinalities? (thus making normal uses cast it to int) Why would len() want to define a type more specific than the equivalent of inserting the symbols " 5 " into the parse stream?
 On reflection, maybe this was aiming too low. Maybe it is const type assignment that should be made even more just in time for Go2. I am now sitting here thinking what the implication of this rule would be: never assign a type to a const expression unless absolutely unavoidable and then unassign that type as soon as is possible.
Some examples:
const pdp1140mem = ^uint16(0)
evaluated as
a zero of no type, "0"
forced to be uint16, giving 0b00000000_00000000
all 16 bits inverted, giving 0b11111111_11111111
returned as a value, so untype(expr) to give the typeless "65535"
This is great for me, but is complicated if the developer then tries
const pdp1140mask = ^pdp1140mem
because this has potentially confusing meanings. (not confusing mathematically, just that masking a high-one and inverting would not turn that leading zero into a one as may be expected if they are thinking the constant has 16-bittedness as an attribute.
Alternatives that work are:
const pdp1140mem uint16 = ^uint16(0)
const pdp1140mask = ^pdp1140mem

or
const pdp1140mem = uint16(^uint16(0))
const pdp1140mask = ^pdp1140mem

or
const pdp1140mem = ^uint16(0)
const pdp1140mask = ^uint16(pdp1140mem)

These all make sense, but highlight the breaking changes that newly understood ultra late type binding and rapid unbinding would bring. In their defense, they could be automagically rewritten by the gofix tooling.
About pure functions
Not only the math functions, but math/bits as well. I have had constants that could wisely be done as const to help the compiler but I could not do it other than via init functions or as a variable. I mused a few months ago about pure functions and compile-time evaluation. It would be great as a general facility, but for the restricted domain of math special functions and bit shuffles/reversals and the like, this could indeed be handled by a single switch statement, almost instantaneous evaluation, and then a happy typeless constant would result for the benefit of the compiler's future optimizations.

Here's a nice motivating example for pure functions, from runtime/stack.go:
const (
	// The minimum stack size to allocate.
	// The hackery here rounds FixedStack0 up to a power of 2.
	_FixedStack0 = _StackMin + _StackSystem
	_FixedStack1 = _FixedStack0 - 1
	_FixedStack2 = _FixedStack1 | (_FixedStack1 >> 1)
	_FixedStack3 = _FixedStack2 | (_FixedStack2 >> 2)
	_FixedStack4 = _FixedStack3 | (_FixedStack3 >> 4)
	_FixedStack5 = _FixedStack4 | (_FixedStack4 >> 8)
	_FixedStack6 = _FixedStack5 | (_FixedStack5 >> 16)
	_FixedStack  = _FixedStack6 + 1
)

A pure round-up-to-power-of-two function would be nice instead.
That said, I think this was the only time that I missed using pure functions in const expressions in 6 years of writing Go.

Alas the round-up-to-power-of-two function does require an if test for "am i already a power of two" or else what you have here. With the if passed to prove not 2^n, then it can be a simple shift by leading zeroes. Without C's ternary operator or the Algol like a := if b then c else d fi, you must have the code you show (with the missing ">> 32" last step for generality).
We could add this to bits, and then with pure function support it would be there for you.
func RoundUpPowerTwo(n uint64) uint64{
switch{
case n=0:
return 1
case (n&(n-1)) == 0: // already a power of two
return n
default: // next higher power of two
return 1<<bits.LeadingZeros64(n)
}
}

I'm very much sympathetic to this idea - it would indeed be nice to have an "untype" mechanism. I also agree that most of these problems would disappear if some of the built-in functions such as len, cap, and the unsafe functions would not return an int but an untyped integer (which would default to an int upon assignment to a variable) if we have a constant expression. (I should look into this, it may be possible to do this in a backward-compatible way).
There may still be a need to explicitly remove a type for which we might want to have an untype built-in that takes a typed value where the underlying type is any of the built-in types, and which simply removes that type.
Regarding your specific example at the top, computing wordBytes as an untyped value, that can be done easily w/o any of this, though. See math/bits/bits.go at the top for an example (it can be refined).
Finally, we actually do have a mechanism in the language to remove type information from numeric values ! :-) That operation is (left or right) shift. Shifts are the only operation that take two operands of different types to produce a result of one of those types (the type of the left operand). If the left operand is untyped, then the result remains untyped no matter the type of the right operand. This can be used to assemble any number from untyped bits. Here's an example:
package main

import "fmt"

const (
	// typed x
	x byte = 0x5b // 0b_0101_1011

	// untyped bits of x
	b0 = 1 - 1>>(x>>0&1)
	b1 = 1 - 1>>(x>>1&1)
	b2 = 1 - 1>>(x>>2&1)
	b3 = 1 - 1>>(x>>3&1)
	b4 = 1 - 1>>(x>>4&1)
	b5 = 1 - 1>>(x>>5&1)
	b6 = 1 - 1>>(x>>6&1)
	b7 = 1 - 1>>(x>>7&1)

	// create an untyped u from the untyped bits of x
	u = b0<<0 | b1<<1 | b2<<2 | b3<<3 | b4<<4 | b5<<5 | b6<<6 | b7<<7

	// verify that u is untyped
	// (if it were typed we couldn't assign it to a complex128)
	_ complex128 = u
)

func main() {
	fmt.Println(b7, b6, b5, b4, b3, b2, b1, b0)
	fmt.Printf("%08b == %08b (%v)\n", x, u, x == u)
}

The scheme can be applied to any numeric built-in type (it gets a bit tricky for floats though), it's source code size is just O(n) where n is the number of bits of the original value... - fun, fun, fun!

I added #31795.

PS: If len would return an untyped integer for a constant expression, one could do len((*[x]byte)(nil)) to remove the type of x.

@MichaelTJones Do you think that @griesemer 's alternate proposal #31795 would address the use cases of an untyped conversion?

ping @MichaelTJones

Closing, as @MichaelTJones replied at https://github.com/golang/go/issues/31795#issuecomment-496729449 that #31795 would be work instead.

I'm fine with closing this, but for the record, @MichaelTJones reply came before I mentioned that we couldn't do #31795 in a backward-compatible way for the unsafe.Sizeof/Alignof/Offsetof functions because they return a uintptr. (I suspect one of the common use cases is wanting to have the size of a type as an untyped value, which would require unsafe.Sizeof.) But we could provide a trivial gofix (or even gofmt).

Much Griesmer-shifting is in my future, but it will work. That's really the
question--is there a workable solution? Yes there is, so ok.
On Wed, May 29, 2019 at 9:59 AM Robert Griesemer<EMAIL_ADDRESS>wrote:

I'm fine with closing this, but for the record, @MichaelTJones
https://github.com/MichaelTJones reply came before I mentioned that we
couldn't do #31795 https://github.com/golang/go/issues/31795 in a
backward-compatible way for the unsafe.Sizeof/Alignof/Offsetof functions
because they return a uintptr. (I suspect one of the common use cases is
wanting to have the size of a type as an untyped value, which would require
unsafe.Sizeof.) But we could provide a trivial gofix (or even gofmt).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/31076?email_source=notifications&email_token=AB4DFJI4Z6AZVCNNHIN4D2DPX2Y7RA5CNFSM4HBW24TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWP7DEA#issuecomment-497021328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4DFJKVWDQSFMR4R5WX4RTPX2Y7RANCNFSM4HBW24TA
.

--
Michael T<EMAIL_ADDRESS><EMAIL_ADDRESS>

Turns out #31795 was closed.
@MichaelTJones, do you want this re-opened?

Nope. It is not a problem for others and workarounds have been shared.
On Tue, Dec 3, 2019 at 2:52 PM Brad Fitzpatrick<EMAIL_ADDRESS>wrote:

Turns out #31795 https://github.com/golang/go/issues/31795 was closed.
@MichaelTJones https://github.com/MichaelTJones, do you want this
re-opened?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/31076?email_source=notifications&email_token=AB4DFJINQF4GFH6AVVJE5UTQW3PL5A5CNFSM4HBW24TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF3DBKI#issuecomment-561393833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4DFJPSWQCYUVYLDFP42QLQW3PL5ANCNFSM4HBW24TA
.

--
Michael T<EMAIL_ADDRESS><EMAIL_ADDRESS>


Issue with Inline Button Titles on iOS Devices

There is an issue with displaying inline button titles on iOS devices.
For some reason, buttons sent using the latest version of this library display their titles correctly on the desktop version of Telegram, the web version, and the Android version, however, on the iOS version, the title simply doesn’t render.
iOS:

macOS desktop:

web.telegram:

At the same time, other messages sent using different libraries show titles correctly across all systems, including iOS (the same iOS device and the client version). So probably we can rule out the problem being on the Telegram client side.
This behavior has been tested on various devices, including the latest versions of Telegram.
Long investigation by our team led to the creation of this issue.
Do you have any thoughts on this?
__
Telegram.Bot: v22.2.0
Code example:
*
var playButton = InlineKeyboardButton.WithWebApp("Play Hyperloop", playButtonUrl);
var markup = new InlineKeyboardMarkup()
    .AddButton(playButton);

await _botClient.SendMessage(chatId, message, parseMode: parseMode, replyMarkup: markup);

contact me in pm @wiz0u so i can analyze the problem better

please test https://github.com/TelegramBots/Telegram.Bot.Examples/tree/master/MiniApp
InlineKeyboardButton.WithWebApp("Launch Mini-App", webappUrl) is sent on /start and displays fine.

the button with a little arrow is a Url button, not WebApp
so you're not comparing the same things anyway.
If your team want to compare things, make sure they take a look at exactly the same message using the different clients.


Docker: Unsupported config option for services.recyclarr: 'init'

Trying to setup a docker instance, but it errors out with the following:
ERROR: The Compose file './docker-compose.yml' is invalid because: Unsupported config option for services.recyclarr: 'init'
I'm running Docker version 20.10.12, build e91ed57
&
docker-compose version 1.22.0, build f46880fe

Did you specify version: '3.9' at the top of the docker-compose.yml file?


Privacy Policy

To be compliant with both national and international regulations, like the GDPR legislation, Progressive Pest Control must have a privacy policy document that discloses the ways in which a website collects, processes, stores, shares, protects user data, the purposes for doing so and the rights of the users.

Legal document for privacy policy.


Parsing html

I don't know if this is an issue of the library or the server itself but you cannot send a message with this text: " Hello Boss im here" because the bot doesn't receive it. It cannot be cursive and bold at the same time for some reason so, the correct way to get that working would be: "Hello Boss  im here"
Can you confirm that this is en telegram issue or is it an library one ?

You can verify this yourself by using the http api to try it.
Kind regards,
Martijn Verbakel

Op 24 feb. 2017 om 21:45 heeft DoomAngels<EMAIL_ADDRESS>het volgende geschreven:
I don't know if this is an issue of the library or the server itself but you cannot send a message with this text: " Hello Boss im here" because the bot doesn't receive it. It cannot be cursive and bold at the same time for some reason so, the correct way to get that working would be: "Hello Boss im here"
Can you confirm that this is en telegram issue or is it an library one ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have read the telegram info and they say that you cannot have tags inside tags so it's OK it's something that they have set like this, not an api fault


chore: migrate CI/CD to infra.ci.jenkins.io

Updating to fix hadolint errors

1 rule fixed
1 rule ignored (with a comment to explain)

Update: as there are 2 images (same lifecycle, same tag policy, but one depends on the other), let's merge them into a single Dockerfile and use a Docker Bake file


[cleaning up] taking out random notebooks (?)

I recently noted that github detects tofu like 58% jupyter notebook. I couldn't understand how it's possible, and then I found various notebooks that seem to me that shouldn't be in the library ?

Codecov Report

Merging #449 (2f4853b) into devel (7ebac68) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            devel     #449   +/-   ##
=======================================
  Coverage   39.97%   39.97%
=======================================
  Files          75       75
  Lines       25154    25154
=======================================
  Hits        10056    10056
  Misses      15098    15098

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 7ebac68...2f4853b. Read the comment docs.

You're right, good point, the notebooks shoudn't be part of the library.


Added support for integer suffixes, e.g. 1k, 8mb

Coverage decreased (-0.08%) to 89.555% when pulling 6f9e4d65124b7ffd990f0cb492af64f21b9014af on dconf into 5c69f82d84aaad28409e42fc888f2085e483c483 on master.


add tests for bypass document validation

fixes #1023
(restoring a mistaken branch deletion)

That's a good catch.  I'm pretty sure it'll need something, too.

Two things:

yes, it needs a test for this
The API is broken enough to make this difficult.  I'd like to defer this to the 1.4 release.

Please elaborate.  What exactly is too broken to fix now?  I'd rather not partially support bypassDocumentValidation if we can help it.

Actually, i just thought of a way to test this with the current API.  stand by...

Aggregate with $out looks good.  How about insert?

I'll merge then if there are no other comments.

I still need to review the latest patches.


Remove timeouts in acme logging middleware

Pull Request Motivation
Logging middleware probably isn't the place for this in any case, but more broadly there's little need to add additional timeouts here; there's an argument for having the logging itself have a timeout, but these timeouts don't achieve that in any case.
This was spotted in this comment and this PR should be merged before #5157 can be merged.
Kind
/kind cleanup
Release Note
Removes context timeouts imposed by ACME logging middleware

/cherry-pick release-1.7

/cherry-pick release-1.8

/test pull-cert-manager-e2e-v1-24

Thanks @SgtCoDFish
This timeout isn't a timeout for the logger itself though, it is the timeout that is passed in a context with to all calls to go/x/crypto acme client and used actually being used there as far as I can see (for example if you follow where the context ends up used in AuthorizeOrder. Do we now if/how the behaviour will change with this PR?
I see that this was added to fix a bug in https://github.com/cert-manager/cert-manager/pull/2713

As I mentioned to @irbekrm after our standup this morning, I think this PR will be needed but I don't think just having a PR removing this is the way to go. I think this stuff will be removed as part of a larger PR, and I'm gonna close this one.


NclientV2 App kept crashing and wouldn't responed

Your issue may already be reported!
Please search on the app kept crashing when trying to open and wouldn't respone before creating one.
Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

There is no invalid response in the main page
Debug Client v2 wouldn't show up all the mangas.
3.N/A
4.N/A
5.N/A

Context

Your Environment

Version used:
Operating System version:

NHentai link (if relevant):

can use version 2.9.4 apk

clone origianl versoin 2.9.4 ( https://github.com/Dar9586/NClientV2/releases/download/2.9.4/NClientV<IP_ADDRESS>.Release.apk ) with "lucky patcher" or else software, then the application will be able to install next to the original, and you will not lose data. or remove the current version


Reaction buttons example and activity id

Version
4.11
Describe the bug
First, I'm not sure if this is the best category for my input.
In the sample for reaction buttons the activityId is passed in the MessageReaction object which does not seem to be part of the specification bot builder implementation.
Also, MessageRection.cs has a type property for the reaction which is not used in the sample to populate the reaction.
Steps to reproduce
See implementation in the sample
const handleUpvoteButton = useCallback(() => {
    postActivity({
      type: 'messageReaction',
      reactionsAdded: [{ activityID, helpful: 1 }]
    });
}, [activityID, postActivity]);

Expected behavior
Shoudn't the activityid be transported via the replyToId activity property and the reaction in the type of "MessageReaction"?
Like this:
    const addMessageReaction = (helpful: boolean) => {
        props.postActivity({
            type: 'messageReaction',
            reactionsAdded: [{ type: (helpful ? "ThumbsUp" : "ThumbsDown") }],
            replyToId: props.activityId
        });
    }

This way, it would be easier to handle the reactions out of the box with c# bot builder sdk:

[Bug]

Thanks for bringing this up. I recall the same thought occurring to me in the past but I failed to follow-up. Your suggestion makes sense to me, and of course we don't enforce any of the code suggestions we make in our samples, so you are free to follow your example code. 🙂
I will bring this up as team discussion to reach a consensus to decide if we want to update the sample.

We will look to prioritize this in the upcoming release.

Assigning to Post R12.
I think the last time we discussed was to fix this shortly after we ship R12. Please correct me if I am wrong.

Originally filed by @5Heinzelmann:

https://microsoft.github.io/BotFramework-WebChat/05.custom-components/d.reaction-buttons/
Screenshots

Steps to reproduce

Go to https://microsoft.github.io/BotFramework-WebChat/05.custom-components/d.reaction-buttons/
Text Hi
Text Help
Wait a few seconds
See error

Expected behavior
Bot answers with default help text and shows reaction buttons in front of each bot message.
Additional context
Same for Chrome and Firefox (I used chrome for Screenshot)
[Bug]


Come up with app name and logo

[ ] Name
[ ] Logo

Name Ideas

Zap
Spark
Surge
Flash
Bolt

https://www.canva.com/design/DAFrTzDvucQ/oIPA9fmyfAZEr-1J9w4BXA/edit?utm_content=DAFrTzDvucQ&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton


2FA with authenticator apps

As suggested by @skoruba it's important to support 2FA.
Here's one way of doing it:
https://dzone.com/articles/aspnet-core-two-factor-authentication-using-google
Basically app installed on you phone and QR code presented in UI:
https://play.google.com/store/apps/details?id=com.azure.authenticator&hl=en_US
https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=en
And excellent tutorial from @damienbod on the topic of 2FA itself in IS4:
https://damienbod.com/2017/07/14/implementing-two-factor-authentication-with-identityserver4-and-twilio/
This way it's more accessible to everyone because you don't have to setup Twillio account and pay for sending messages.

Done on master.


generate unambiguous class and method names

When compiling proto files that define the same service name in different packages (such as these), Template.java ends up containing duplicate class and method names, and compileJava fails, as reported in #5.
This PR addresses the issue by generating class names that include the package path, such as SomeserviceV2SomeService.

thanks!


Load plantUML from image link

Thanks for doing this the editor it looks great!
If I create a diagram say for github but then I want to edit it, is there a way to load the diagram back into the editor?
Say I have:
<img src="https://plantuml-server.kkeisuke.app/svg/[encoded-plantuml-code].svg"/>

How can I load this into the editor? I can't seem to find a way to do it.
Perhaps it would be good to make a route where it is possible to pass in the image url to load it into localStorage in the editor? Eg.
https://plantuml-editor.kkeisuke.com?img=https://plantuml-server.kkeisuke.app/svg/SyfFKj2rKt3CoKnELR1Io4ZDoSa700.svg
Then this could become a dialog that accepts a url?

I found a python script to decode the string perhaps it could be ported over to JS?
https://gist.github.com/ryardley/64816f5097003a35f9726aab676920d0

Hey, I actually needed the same thing and I added it in my fork here: https://github.com/alinradut/plantuml-editor
Also disabled automatic local storage saves and added history pushstate/popstate.
I probably implemented this the wrong way as far as vue is concerned, but it works for me.


Large scale benchmark of batch algorithms

use only test functions with variable number of dimensions: 2,4,8,16,32,64 ..., 65K

The maximum number of dimensions should be read from command line

Implement a range of dimensions to consider: "--min-dims=1 --max-dims=10000". Thus can perform both small and large scale experiments. Add also the number of trials as a command line parameter.


Gradle build finished with 1 error(s) and 1 warning(s)

Module Gradel:

// 编译【compile】RxJava
compile 'io.reactivex:rxjava:1.2.2'
// 编译【compile】RxAndroid
compile 'io.reactivex:rxandroid:1.2.1'
// 编译【compile】RxLifecycle(解决RxJava内存泄露问题,包含以下三个【Solve the problem of RxJava memory leaks, includes the following three】)
compile 'com.trello:rxlifecycle:1.0'
// If you want to bind to Android-specific RxLifecycle
compile 'com.trello:rxlifecycle-android:1.0'
// If you want pre-written Activities and Fragments you can subclass as providers
compile 'com.trello:rxlifecycle-components:1.0'

我依赖了3个,但是Gradle出错了【I rely on the three, but Gradle went wrong】:
Warning:Conflict with dependency 'com.google.code.findbugs:jsr305'. Resolved versions for app (3.0.1)       and test app (2.0.1) differ. See http://g.co/androidstudio/app-test-app-conflict for details.
Error:Execution failed for task ':app:prepareDebugAndroidTestDependencies'.

Dependency Error. See console for details.

能帮帮我么？【Can help me?】

You'll need to compile all your sources with a specific version of com.google.code.findbugs:jsr305 so that they don't conflict in the test app.

@dlew  thanks.
In the project build. Gradle Android with {}:
configurations.all {
        resolutionStrategy.force 'com.google.code.findbugs:jsr305:3.0.0'
}

Problem solved.