Correctly handle IAC byte escaping

I noticed that IAC character escaping (double 0xFF) was not working quite correctly. The buffer in the event returned after the escaped IAC character was re-copying data because data_start was not being updated.
I've added a test to lib.rs to verify the fix.

Please hold off on merging this, if you're looking at it. I need to write a new test, because I appear to have broken normal IAC command handling. Oh bother.

Update: I was wrong, further tests prove that I did not break normal IAC command handling. I only thought I had, because of user error (I accidentally set the buffer size to 1 byte when creating my Telnet object, which is really not useful at all :) )

Hello @sethm ! I just check your commits. You found a really big bug in my code. I appreciate your contribution. Thanks for your help :)


[bug] timestamp behaves like timestampz -  includes timezone when editing

Bug report
Describe the bug
timezone is being added to timestamp data
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
https://user-images.githubusercontent.com/8291514/131619696-479bfc44-4a60-4184-be7e-7d2acdf25bc8.mov
Expected behavior
Should it be no timezone for timestamp ?

fixed: https://github.com/supabase/grid/commit/f172687f6fe1f519212f4c88559e2e5e595f8018, https://github.com/supabase/grid/commit/1f22bd039f5803ad6029016345b7c4f04320fecf


Need better README

It would be helpful if you could provide a better README for this. :+1:
Maybe someone can collaborate

Thanks for you interest. I have been busy with my day job to continue the
project. Will post progress soon.
FYI
This is a rpi project i am doing for feeding my pet automatically in
duration or remotely manually
On Thu, Jan 21, 2016 at 1:28 PM, Khirod Kant Naik<EMAIL_ADDRESS>wrote:

It would be helpful if you could provide a better README for this. [image:
:+1:]
Maybe someone can collaborate
—
Reply to this email directly or view it on GitHub
https://github.com/shubhamsha12/Pet-Feeder/issues/1.

--
Cheers
Shubham Sharma


Error renderer "in line" link should include the line number

Testing #172096
It's not clear if this link goes to the active line because of https://github.com/microsoft/vscode/issues/172206, but I think it should and the link should also include the line text, similar to the terminal

Unfortunately the link is from the kernel in the form of html link in line 2 so we are not doing another syntax detection to include the line 2 into the link right now. It's a nice to have feature.


ResponseStatusCode ensure, assert, expect and failure continuations

expect and assert pass through the original response. Failure continuations can be achieved with Result.mapError.


Visualization of Receptor Fingerprint

The statistics must be added to the y-axis when displaying the receptor graph.
Receptor density (fmol/mg protein +- SD) or STD (this is written in the tabular).

Solved with 769663b75a0b50106b2377f245d6e3ecfc0dbd06. The change will be seen on siibra-explorer with the next version.


GetEntities: "Path not rooted" exception

When executing the code below with this zip, I get a ParseException ("Path is not rooted") from FileSystemPath.Parse. Am I using it wrong, or is this a bug?
        static void Main(string[] args)
        {
            using (var stream = System.IO.File.OpenRead("sample.zip"))
            using (var fs = SharpFileSystem.SharpZipLib.SharpZipLibFileSystem.Open(stream))
            {
                foreach (var e in fs.GetEntities(FileSystemPath.Root))
                {
                    Console.WriteLine(e.EntityName + " - " + e.Path);
                }
            }
            Console.ReadKey();
        }

SharpZipLibFileSystem has not been used for quite a while. I've just pushed a number of unit tests, that cover your problem and fixed the problem in SharpZipLibFileSystem. Please close this issue if this fixes your problem as well.

I'm sorry it took me so long to respond. The latest code is working great for me. Thanks!


plots: clarify (more) that stage-level plots can be dirs

per https://github.com/iterative/dvc.org/pull/3940#issuecomment-1251843556

Found an old issue that this should fix: https://github.com/iterative/dvc/issues/5216. It mentions dvc run, so we should update that and stage add for the --plots/--plot-no-cache options. Do you want to add that here? Happy to take that if it's easier.

Good find @dberenbaum ! I'm not supposed to spend much time working on cmd refs though. Trying to focus on higher level content. But if this is approved so far please merge it or take it over within your team 🙂


Use pprof::* types directly in more places

What does this PR do?
This reduces the number of object conversions, so we end up with less
lines of code.
This also bumps a variety of versions, editions, and dependencies. This
probably should have been a separate PR, sorry.
Motivation
I was bothered by the number of extra structs and copying code, so I
thought I'd take a look and it was easy enough to replace some of the
types.
Additional Notes
I ran cargo test but wasn't sure if there's anything else to do to
check that I didn't break telemetry.
This is technically a breaking change for the Rust side of the API, but
nobody is using it in production yet. The FFI side is stable.
How to test the change?
cargo test should be enough.

This is a draft at the moment because I should probably test the Hash and Eq implementations for the pprof types to be sure I didn't screw it up.

Oops, wrong repo :facepalm:


run android take a long time

Hi . i just add react-native-popup-dialog and paste your example code in my App.js but  npm run android take too much time

Lol, what I can help?


Add Maven Central badge to README.md

Thanks to the badge the version information never has to be updated again:

it's always up to date
plus on the Maven Central page you have
dependency management templates for non-Maven users
download link to JAR (no need to keep it on restfb.com)

Added to dev, thx a lot


Bluetooth: Shell: Fix off-by-one in address length validation

Fixes Coverity defect id 248346.
Fixes https://github.com/zephyrproject-rtos/zephyr/issues/45072.
Signed-off-by: Aleksander Wasaznik<EMAIL_ADDRESS>

I manually created an issue: https://github.com/zephyrproject-rtos/zephyr/issues/45072. I could not find one by zephyrbot.


[Bug]: Incorrect  word wrapping

Browser
Firefox
Package version
v3.0.311
React version
v18.2.0
Description
The split panel's word-wrapping does not correctly account for large contiguous header strings. Specifically the word-wrap property is set to break-word however if a header contains a long contiguous string this behaves incorrectly. Because of this incorrect word wrapping the split panel when used in the side layout overflows and forces uses to horizontally scroll. The solution for this should be very simply simply add an additional CSS property here for word-break set to break-all to ensure there's no overflow even if it's a long contiguous string.
Source code
No response
Reproduction
Simply create a split panel with a long string set as the header value, limit the maximum size of the split panel to something small and then set the split panels position to side.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems

For what it's worth this same behavior also seems to be impacting table cells, it would be great if we could also break-all there for consistency.

Fixed in v3.0.359


The discord notification workflow fails on single quote in mod description

https://github.com/neos-modding-group/neos-mod-manifest/actions/runs/3790202585/jobs/6444641922#step:6:1
https://github.com/neos-modding-group/neos-mod-manifest/actions/runs/3577158302/jobs/6015832575
basically the action calls curl with some data like
curl -d '{"description":"you're"}' '***'

which crashes because of the single quote inside the word "you're" ends the data part of the request specified by the -d flag
I think to fix this it would be as simple as replacing all ' with '\'' which seems to be the escape character for quotes in bash

\ needs to be escaped as well in addition to ', but yeah. The notification thing was a quick'n'dirty hack, so I'm amazed it's managed to go this long without totally breaking down x'D

ive created #202 as a potential fix for this issue

huh, guess github decided to auto close this issue, i reran the failed action for #198 and it failed. not sure why #200 did not fix the issue

Github auto closed it because it was titled 'fixes # 202' and then merged

This was fixed in #205 and should probably be closed.


fix: Fallback to isTypeSupported when cast namespace is undefined

Resolves #5010

@littlespex is it ready for review?

I'm waiting on verification on a few other devices. I will pull it out of draft later today.

@avelad Verification is complete and the PR is ready for review.

@JulianDomingo, can you review it?, if I remember correctly you implemented this part.

LGTM, but I would like Julian to confirm.  I'll do a test run in the lab to be certain it doesn't break existing test cases.


The requested module /node_modules/.vite/@mdx-js_react.js?v=d545b648 does not provide an export named mdx

Originally posted by @hfabio in https://github.com/brillout/vite-plugin-mdx/issues/44#issuecomment-1039856954

Just wanted to add a bit more helpful info for others who venture here. I was successful with these steps:

Did not set type: "module" in my package.json. For me this caused a ton of other issues.
Added the MDX plugin in my vite.config.ts like this:

import { defineConfig } from 'vite';

export default defineConfig(async () => {
  const mdx = await import('@mdx-js/rollup');

  return {
    plugins: [mdx.default()]
  };
});

Had to set "target": "esnext" in my tsconfig.json otherwise I was getting transpilation errors

Does someone faced this kind of error?
Uncaught SyntaxError: The requested module '/node_modules/.vite/@mdx-js_react.js?v=d545b648' does not provide an export named 'mdx'

I'm using:

react - ^17.0.2
vite - ^2.5.3
@storybook/react - ^6.4.19
storybook-builder-vite - ^0.1.15
@mdx-js/react -^2.0.0
@mdx-js/rollup - ^2.0.0
vite-plugin-mdx - ^3.5.10

This is my .storybook/main.js:
module.exports = {
  stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
  addons: ['@storybook/addon-links', '@storybook/addon-essentials'],
  core: {
    builder: 'storybook-builder-vite',
  },
};

and this is my vite.config.ts:
import { defineConfig } from 'vite';
import camelCase from 'camelcase';
import * as path from 'path';
import * as fs from 'fs';
import dts from 'vite-plugin-dts';
import eslint from 'vite-plugin-eslint';
import reactRefresh from '@vitejs/plugin-react-refresh';
import mdx from '@mdx-js/rollup';
import pkg from './package.json';

// `options` are passed to`@mdx-js/mdx`
const mdxOptions = {
  // See https://mdxjs.com/advanced/plugins
  remarkPlugins: [
    // E.g. `remark-frontmatter`
  ],
  rehypePlugins: [],
};

const getEntry = () => {
  const tsxFile = path.resolve(__dirname, 'src/index.tsx');
  if (fs.existsSync(tsxFile)) return tsxFile;
  const tsFile = path.resolve(__dirname, 'src/index.ts');
  if (fs.existsSync(tsFile)) return tsFile;
  throw new Error('Cannot find entry. (src/index.tsx or src/index.ts)');
};
// https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    reactRefresh(),
    eslint({ fix: true, throwOnWarning: false }),
    dts({ tsConfigFilePath: './tsconfig.build.json', insertTypesEntry: true }),
    mdx(mdxOptions),
  ],
  esbuild: {
    jsxInject: "import * as React from 'react';",
  },
  build: {
    lib: {
      entry: getEntry(),
      name: camelCase(path.basename(pkg.name)),
      fileName: (format) => `index.${format}.js`,
    },
    rollupOptions: {
      external: ['react', 'react-dom', 'styled-components'],
      output: {
        globals: {
          react: 'React',
          'react-dom': 'ReactDOM',
          'styled-components': 'styled',
        },
      },
    },
  },
});

Have you tried deleting your node_modules/.vite folder?

Have you tried deleting your node_modules/.vite folder?

no, I didn't, and the time was passing, so I aborted the idea...


Add um2netcdf CI entrypoint

Closes #82.
This PR adds CI config to:

Add an entry point for um2netcdf
Run a simple check to call the command

Any comments welcome!

I've added the open question to #87.


Feature request: select date range

Often times you want to select a starting date and a finishing date (hotel, trip).
It would be great to be able to do it with this element, maybe adding a "range" or "multi" or whatever flag

Awesome element btw :)

I am not sure but I think what you want is able by using min-date and  max-date am I right?

Hmm no, min/max-date doesn't allow the user to pick 2 dates, it just allows the user to pick 1 date within a range, right?
I want to get 2 dates out of the date-picker element, and highlight the dates in between if possible.

Oh sorry I did not understand what you mean...
Effectively I do not think the feature you mentioned exist any more, what I mentioned was to pick only one date within a range like you say, another time sorry for my mistake ;)

The MD spec doesn't cover the UX for this, and this component is intended to be (within reason) a reference implementation. So, I'm hesitant to change the component much to add this functionality when it can be done more simply with two date fields.  I would, however, be interested in seeing mock-up ideas for how this might work while not straying too far from the spec.
If it makes sense to pull paper-calendar out into a separate component that would allow for more customization, I'd be more apt to do that, and add some more fine-grained features to paper-calendar, such as tracking an array of disabled / allowable dates (see #113), and a "range" mode.

Thanks that makes sense. I actually used 2 date pickers (one for start and one for end data), which is more than enough.
I think that a feature such as the one described in #113 would be a perfect alternative (Angular team included it in theirs Date Picker implementation ([1]).
[1] - https://material.angularjs.org/latest/demo/datepicker

Anyone implemented date range using this datepicker ? Yes, date range would be great addition to this plugin as it is a frequently used feature.

Not yet. There is edk-date-picker, which has this feature, but it is outdated.

Here is a new range date picker just released : https://github.com/RoXuS/range-datepicker


Allow Scaling Collision Meshes

Description
This PR allows users to scale a collision mesh when adding it into the planning scene. Note that scaling occurs within the mesh's XYZ axes.
This PR also adds trimesh as a dependency. Although it is not a required dependency (it is only necessary when using meshes), I think it is beneficial to add so that all possible dependencies can be installed with a single rosdep call.
Testing

[x] Launch the simulated panda arm: ros2 launch panda_moveit_config ex_fake_control.launch.py
[x] Add a collision mesh, verify it is the expected scale: ros2 run pymoveit2 ex_collision_mesh.py --ros-args -p position:="[0.5, 0.0, 0.5]" -p quat_xyzw:="[0.0, 0.0, -0.7071, 0.7071]"
[x] Re-add the collision mesh with a scaled X, verify it updates as expected in RVIZ: ros2 run pymoveit2 ex_collision_mesh.py --ros-args -p position:="[0.5, 0.0, 0.5]" -p quat_xyzw:="[0.0, 0.0, -0.7071, 0.7071]" -p scale:="[0.5, 1.0, 1.0]"
[x] Re-add the collision mesh with a scaled Y, verify it updates as expected in RVIZ: ros2 run pymoveit2 ex_collision_mesh.py --ros-args -p position:="[0.5, 0.0, 0.5]" -p quat_xyzw:="[0.0, 0.0, -0.7071, 0.7071]" -p scale:="[0.5, 2.0, 1.0]"
[x] Re-add the collision mesh with a scaled X, verify it updates as expected in RVIZ: ros2 run pymoveit2 ex_collision_mesh.py --ros-args -p position:="[0.5, 0.0, 0.5]" -p quat_xyzw:="[0.0, 0.0, -0.7071, 0.7071]" -p scale:="[0.5, 2.0, 5.0]"

I'm fine either way, because if we don't add it to pymoveit2's mandatory dependencies, then I'll just add it to the mandatory dependencies of my package that uses pymoveit2.

In general, I believe it is best to keep Python packages out of the manifest (they might not be handled properly like setup.py or pyproject.toml dependencies).

In my experience, for ROS projects it's easiest to manage all dependencies with rosdep. That way, a single command can do the installation across all packages in the workspace, which makes it easier for new team members to onboard. rosdep certainly has its limitations---like not being able to properly handle version numbers for Python dependencies, and using sudo for pip dependencies---but in my experience the benefits outweigh the drawbacks. In order to use a single rosdep command for all dependencies, all dependencies need to be specified in package.xml.
I haven't used ROS/ROS2 with a virtual environment, and I understand how that could get complicated. It seems like at least one person has been able to get rosdep working with venv.

The user also already gets an explanatory error if they are missing the package when calling the appropriate function.

I agree that this error is very helpful (and more than other open-source libraries do 😄  ).

I went ahead and removed trimesh as a required dependency.


[Feature Request]:  styling the update password page

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
styling the update password page
Use Case
styling the update password page
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

/assign

@Meetpidev #458 is same ryt?

YUP.. I will reset the title..

YUP.. I will reset the title..

DONE..

@Meetpidev so i will close this


Add condition before socket factory setting

Purpose

Fixes wso2/product-apim#11730

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/1274371130

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/1274371130
Status: success


Error runing quantization_speedup.py

Describe the issue:
When running quantization_speedup.py in the tutorial file (I did not change anything), I got an error as below.
[2022-07-20 01:41:46] Model state_dict saved to ./log/mnist_model.pth
[2022-07-20 01:41:46] Mask dict saved to ./log/mnist_calibration.pth
[07/20/2022-01:41:49] [TRT] [W] DynamicRange(min: -0.424213, max: 2.82149). Dynamic range should be symmetric for better accuracy.
Traceback (most recent call last):
  File "quantization_speedup.py", line 114, in <module>
    engine.compress()
  File "/opt/conda/lib/python3.7/site-packages/nni/compression/pytorch/quantization_speedup/integrated_tensorrt.py", line 298, in compress
    context = self._tensorrt_build_withoutcalib(self.onnx_path)
  File "/opt/conda/lib/python3.7/site-packages/nni/compression/pytorch/quantization_speedup/integrated_tensorrt.py", line 348, in _tensorrt_build_withoutcalib
    engine = build_engine(onnx_path, self.onnx_config, self.extra_layer_bits, self.strict_datatype)
  File "/opt/conda/lib/python3.7/site-packages/nni/compression/pytorch/quantization_speedup/integrated_tensorrt.py", line 198, in build_engine
    handle_gemm(network, i, config)
  File "/opt/conda/lib/python3.7/site-packages/nni/compression/pytorch/quantization_speedup/integrated_tensorrt.py", line 82, in handle_gemm
    pre_in_tensor.dynamic_range = (tracked_min_input, tracked_max_input)
AttributeError: 'NoneType' object has no attribute 'dynamic_range'

Environment:

NNI version: 2.8
Training service (local|remote|pai|aml|etc): local
Client OS: Ubuntu20.04
Server OS (for remote mode only):
Python version: 3.7.10
PyTorch/TensorFlow version: 1.9.0
Is conda/virtualenv/venv used?: no
Is running in Docker?: yes
GPU: 3090
cuda: 11.1
Nvidia-tensorrt: <IP_ADDRESS>

Configuration:

Experiment config (remember to remove secrets!):
Search space:

Log message:

nnimanager.log:
dispatcher.log:
nnictl stdout and stderr:

How to reproduce it?:

@Raychen0617 , thanks for reporting this issue, which tutorial did you run?

This one https://github.com/microsoft/nni/blob/e8c78bbab03fa651563e21cdf004220f29d9560a/examples/tutorials/quantization_speedup.py


small fix to transactions.md

Just made a small grammar fix.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4fe4f712cfee12549a502589dadd533ccc5bb5fb/


Compression improvements

[ ] chunk by anything else than store to avoid different sizes in compressed files
e.g. total items / stores
[ ] move all store data from utils into store/*.js and provide via loadItems e.g. stores.compressed.json
[ ] inject the stores with decompress/compress to avoid duplication
[ ] Investigate brotli instead of gzip
[x] #51
[x] Split url compress/decompress data from logic

I'd chunk them by a fixed divisor, e.g. split them up in 5 equally sized
buckets.
On Tue, May 30, 2023, 16:05 Christian Tschugg @.***>
wrote:

chunk by anything else than store to avoid different sizes in
compressed files
e.g. total items / stores
inject the stores with decompress/compress to avoid duplication

—
Reply to this email directly, view it on GitHub
https://github.com/badlogic/heissepreise/issues/44, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD5QBD562EBCCWIUAAN7GDXIX5CFANCNFSM6AAAAAAYUCGWYQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have no idea what items 2 and 3 mean, but I had a quick looksy at Brotli on the CLI.  I'd take that on if you don't mind.

For my raw data, gzip gives me 863mb of compressed data, brotli with quality 9 gives me 457mb, so almost a 50% reduction. Using higher quality settings becomes prohibitive, as brotli takes ages to compress the files.
I'm writing a new migration path. We'll stack the migrations going forward, should we find better ways to compress things.

Awesome 😍

Tada. The migration code is now a bit more generic, the same is true for readJSON and writeJSON. Changes should be mostly self-explanatory.
I've also added migration.js, a simple CLI tool to convert raw data between formats. Examples:
node migrate.js data ".json" ".json.gz"
node migrate.js data ".json.gz" ".json.br"
node migrate.js data ".json.br" ".json

So we can fully round trip things.

Added a simple binary compression scheme. Beats json in both download size (4.8mb instead of 5mb) and decoding speed (~100ms faster)

Welp, got the binary encoding down to 3.8mb. While I was working on that, I improved some general things, which lead to the json encoding now also only taking up 4mb. The json encoding now wins at load times, so it's the default again.

I'm not sure we would gain anything particular by doing the other two open points, so I'm closing this issue


Error + Warnings in permission phasis depending of Android 8.1 or 10

Environment

OS: Windows 10 10.0.19043
CPU: (4) x64 Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
Memory: 2.13 GB / 7.70 GB
Binaries:
Node: 16.14.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.13.1 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
AllowAllTrustedApps: Enabled
IDEs:
Android Studio: Not Found
Visual Studio: Not Found
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.1 => 0.70.1
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Platforms
Win 10 : no problem at build
Versions
1 on And 8.1: with error in metro
1 on And 10 ==API 29 without error

react-native-geolocation:3.0.1
react-native: see up
react: see up

Description
I get in console for both :
WARN  new NativeEventEmitter() was called with a non-null argument without the required addListener method.
WARN  new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.
on And 8.1 terminal ==API27 , I get in addition :
ERROR  {"PERMISSION_DENIED": 1, "POSITION_UNAVAILABLE": 2, "TIMEOUT": 3, "code": 1, "message": "Location permission was not granted."}
and after in both cases the logs :
LOG  Running "test_rn_geoloc" with {"rootTag":11}
LOG  {"coords": {"accuracy": 20, "altitude":<PHONE_NUMBER>964844, "heading": 0, "latitude": 45.5563458, "longitude": 5.5240304, "speed": 0}, "extras": {}, "mocked": false, "timestamp":<PHONE_NUMBER>458}
Reproducible Demo
code in App.js :
`import Geolocation from '@react-native-community/geolocation';
const App = () => {
const [hasPermission, setHasPermission] = useState(null);
//at start : get permissions geoloc
useEffect(() => {
Geolocation.requestAuthorization();
}, []);
Geolocation.getCurrentPosition(info => console.log(info));
return (

 depart

);
};`
and in manifest .xml :
uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" /
Thanks for you ideas !

and on a Android 11 ,
I have in console :
BUNDLE  ./index.js
ERROR  Error: The package '@react-native-community/geolocation' doesn't seem to be linked. Make sure:

You rebuilt the app after installing the package
You are not using Expo managed workflow
WARN  new NativeEventEmitter() was called with a non-null argument without the required addListener method.
WARN  new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.
LOG  Running "test_rn_geoloc" with {"rootTag":1}

and after acceptation on the screen of the authorization :+1:
ERROR  Error: The package '@react-native-community/geolocation' doesn't seem to be linked. Make sure:

You rebuilt the app after installing the package
You are not using Expo managed workflow
, js engine: hermes
then a response:
LOG  {"coords": {"accuracy": 18.87605857849121, "altitude": 0, "heading": 0, "latitude": 45.5865938, "longitude": 5.278462, "speed": 0}, "extras": {}, "mocked": false, "timestamp":<PHONE_NUMBER>258}

Should be fixed in the latest release

ok , thanks ( I do not test)


Documentation for Publish API needs extra info

@42degrees commented on Fri Jun 22 2018
Looking at the documentation at: https://lbryio.github.io/lbry/ for "publish" API (and CLI, presumably) the 'name' field apparently has limitations on what characters can be in the field, but these are not documented. I have discovered through trial and error that at least spaces and commas are not allowed.  I don't know yet if other characters are also disallowed.

@42degrees commented on Fri Jun 22 2018
After digging through the code in lbry/Daemon.py and lbryschema/uri.py I finally found the regular expression governing names is:
valid_name_char = "[a-zA-Z0-9-]"
That is pretty limiting and really should be documented.

Thanks @tzarebczan for putting this in the right place.  Still learning how things are organized.
Also, to add to the above, even after changing my names to only have simple alpha and dash they wouldn't go through.  Apparently there was a name length issue as well.  Once I shortened them up, they worked.  I didn't take the time to figure out the exact limitation, hoping that whoever updates the documentation will already know those limits.

@42degrees Can you reproduce the name length issue again? Or post the logs here with a sample publish that fails. Thanks!

@tzarabczan Here is what I see in the log in these cases.  You can see that the name (Saint-The-500618-02-A-Sonata-For-Slayers-32-22-27m57s-6553) doesn't have anything in it that violates the Regular expression above.  The actual call to publish returns 200.  When I republished this with the shorter name "A-Sonata-For-Slayers" it went through just fine.
2018-06-22 19:35:38,746 INFO     lbrynet.daemon.Publisher:25: Starting publish for Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593
2018-06-22 19:35:38,971 INFO     lbrynet.core.Wallet:1203: Send claim: Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593 for 0.001: 080110011ae7010801129e01080410011a295469746c653a2041205265616c20476f6e65204775790a41697265643a20313935302d30372d30320a221b546865205361696e74202d2041205265616c20476f6e65204775792a00320d5075626c696320446f6d61696e38004a39687474703a2f2f7777772e34326465677265657364657369676e2e636f6d2f696d616765732f7468657361696e746f747273686f772e6a706752005a001a42080110011a305e0350f26e6ee7d63e3a6573103d16b7f4b0c03d5545788a63d0d6ba9d588b106305dfe9e9ffa11d87a70b2cdc0ea0ed220a617564696f2f6d706567
2018-06-22 19:35:39,278 INFO     root:205: using buckets: [u'a75806e7b248d1a1434d821d785ac5c2a74c06cb8210862284f9115cdab569f4:1']
2018-06-22 19:35:42,614 ERROR    lbryum:119: [lbryumx2.lbry.io] serving improperly sorted address histories

2018-06-22 19:35:43,105 INFO     lbrynet.daemon.Daemon:732: Success! Published to lbry://Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593 txid: 9fc3d56269adace93c42accfacd521e7a368da0070576188097ff0a38cec5e70 nout: 0
2018-06-22 19:35:43,114 WARNING  lbrynet.daemon.auth.server:211: error processing api request: Invalid name given to publish
traceback:   File "site-packages\twisted\internet\defer.py", line 1299, in _inlineCallbacks

  File "site-packages\lbrynet\daemon\Daemon.py", line 2039, in jsonrpc_publish

exceptions.Exception: Invalid name given to publish
2018-06-22 19:35:43,121 INFO     lbrynet.daemon.Daemon:2147: Publish: {'claim_address': None, 'channel_id': None, 'name': u'Saint-The-500618-02-A-Sonata-For-Slayers-32-22-27m57s-6553', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'The Saint - A Sonata For Slayers', u'license': u'Public Domain', u'author': u'', u'title': u'Title: A Sonata For Slayers\nAired: 1950-06-18\n', u'language': u'en', 'version': '_0_1_0', u'nsfw': False, u'thumbnail': u'http://www.42degreesdesign.com/images/thesaintotrshow.jpg'}}}, 'channel_name': u'@OTR', 'bid': Decimal('0.001'), 'file_path': u'D:\\mp3\\Saint, The\\Publish to LBRY\\Saint,The - 500618 - 02 - A Sonata For Slayers  - 32-22 27m57s 6553.mp3', 'change_address': None}

The other part of this is that when this happens I get the entry in LBRY showing "Unused" (screen shot attached).
2018-06-22 19:37:13,969 INFO     lbrynet.daemon.Publisher:25: Starting publish for Saint-The-501224-25-Santa-Claus-Is-No-Saint-32-22-28m14s-6621
2018-06-22 19:37:14,173 INFO     lbrynet.reflector.client.client:132: Reflector needs descriptor and 7 blobs for stream
2018-06-22 19:37:14,256 INFO     lbrynet.reflector.client.client:221: Sent reflector descriptor 0afa0122f077e8bc
2018-06-22 19:37:14,594 INFO     lbrynet.core.Wallet:1203: Send claim: Saint-The-501224-25-Santa-Claus-Is-No-Saint-32-22-28m14s-6621 for 0.001: 080110011af701080112ae01080410011a315469746c653a2053616e746120436c617573204973204e6f205361696e740a41697265643a20313935302d31322d32340a2223546865205361696e74202d2053616e746120436c617573204973204e6f205361696e742a00320d5075626c696320446f6d61696e38004a39687474703a2f2f7777772e34326465677265657364657369676e2e636f6d2f696d616765732f7468657361696e746f747273686f772e6a706752005a001a42080110011a3036dcb81459a68a4aac3d4f2d7f59d8d1207ebeaf5734c002e273a5b804a86562b6bc7135b23ade3c6744c606116a6eb2220a617564696f2f6d706567
2018-06-22 19:37:15,270 INFO     root:205: using buckets: [u'6b0c0a7eb6a34f6fd9a06d13cd73471fa6aa8305ef04d5858e7941023f622122:1']
2018-06-22 19:37:18,798 INFO     lbrynet.daemon.Daemon:732: Success! Published to lbry://Saint-The-501224-25-Santa-Claus-Is-No-Saint-32-22-28m14s-6621 txid: bf24d3c369b6c20573046c0a1c8e688a6a4992c925b1e07e19c5b0b533ac1a45 nout: 0
2018-06-22 19:37:18,813 WARNING  lbrynet.daemon.auth.server:211: error processing api request: Invalid name given to publish
traceback:   File "site-packages\twisted\internet\defer.py", line 1299, in _inlineCallbacks

  File "site-packages\lbrynet\daemon\Daemon.py", line 2039, in jsonrpc_publish

exceptions.Exception: Invalid name given to publish
2018-06-22 19:37:18,836 INFO     lbrynet.daemon.Daemon:2147: Publish: {'claim_address': None, 'channel_id': None, 'name': u'Saint-The-510401-39-Simon-Carries-The-Ivy-32-22-27m47s-6517', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'The Saint - Simon Carries The Ivy', u'license': u'Public Domain', u'author': u'', u'title': u'Title: Simon Carries The Ivy\nAired: 1951-04-01\n', u'language': u'en', 'version': '_0_1_0', u'nsfw': False, u'thumbnail': u'http://www.42degreesdesign.com/images/thesaintotrshow.jpg'}}}, 'channel_name': u'@OTR', 'bid': Decimal('0.001'), 'file_path': u'D:\\mp3\\Saint, The\\Publish to LBRY\\Saint,The - 510401 - 39 - Simon Carries The Ivy  - 32-22 27m47s 6517.mp3', 'change_address': None}

@42degrees can you try to see if it's still happening? Can you post what the api call looks like?
I just ran: {"jsonrpc":"2.0","method":"publish","params":{"name":"Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593","channel_id":"","bid":0.00001,"metadata":{"title":"test pub","nsfw":false,"license":"None","licenseUrl":"","language":"en","thumbnail":""},"file_path":"xxxxxx"},"id":1530149530332}
Results:
18-06-27 21:32:10,467 INFO     lbrynet.core.Wallet:1203: Send claim: Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593 for 0.00001: 080110011a6808011220080410011a08746573742070756222002a0032044e6f6e6538004a0052005a001a42080110011a30ec7eb508b1d1031863d3ee066d15b16924cf3d958852dd9fa52f432deb1f06595d1150316f9b44260243bb1ce1f2bc43220a696d6167652f6a706567
2018-06-27 21:32:10,546 INFO     root:205: using buckets: [u'494850264b22c23510b3886607382187026ff1bee82a6ff6122d101d79c4396d:1']
2018-06-27 21:32:12,381 ERROR    lbryum:119: [lbryumx2.lbry.io] serving improperly sorted address histories

2018-06-27 21:32:12,678 INFO     lbrynet.daemon.Daemon:732: Success! Published to lbry://Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593 txid: c0854c868612321c515dab9ebf11b6112b94fef1d25002074a6feaa37083906e nout: 0
2018-06-27 21:32:12,914 INFO     lbrynet.reflector.client.client:132: Reflector needs descriptor and 1 blobs for stream
2018-06-27 21:32:12,963 INFO     lbrynet.reflector.client.client:221: Sent reflector descriptor ec7eb508b1d10318
2018-06-27 21:32:13,091 INFO     lbrynet.reflector.client.client:74: Reflector has all blobs for ec7eb508b1d10318
2018-06-27 21:32:13,095 INFO     lbrynet.daemon.Daemon:728: Reflected new publication to lbry://Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593

Regarding the screenshot, are those related the ones that originally failed to broadcast due to mempool conflicts? Can you send the output of file_list --claim_name=Saint-The-501224-25-Santa-Claus-Is-No-Saint-32-22-28m14s-6621 (or a new one that still hasn't been resolved)

I can send you the LinqPad application that I wrote to upload these, assuming you can read C#.  But here are the important bits:
This is the JSON that I am sending to the daemon:
    var json = $@"
{{
  'jsonrpc': '2.0',
  'method':'publish',
  'params': {{
                'name': '{name}',
                'file_path': '{rootFolder}{filename}',
                'bid': 0.001,
                'channel_name': '@OTR',
                'metadata': {{
                                'description': '{description}',
                                'title': '{title}',
                                'author': '',
                                'thumbnail': 'http://www.42degreesdesign.com/images/thesaintotrshow.jpg',
                                'language': 'en',
                                'license': 'Public Domain',
                                'nsfw': false
                            }}
            }}
}}
";

The code that sends it is straightforward:
    var client = new HttpClient();
    client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
    var publishContent = new StringContent(json, UTF8Encoding.UTF8, "application/json");
    var publishResponse = client.PostAsync("http://localhost:5279", publishContent).Result;
    return publishResponse.IsSuccessStatusCode;

@tzarebczan Unfortunately, I have resolved all of the issues and fully uploaded all of the Saint files.  The Unused entries in LBRY are cruft and are not real.  If I click on any one of them it finds the correct item and no longer shows the Unused.
I was planning to wait until I had the graphical version of the bulk uploader complete before sending any more of them (I'm about half done with it).  I still need to figure out how to send them quickly but not so quickly that I get a bunch of "lbryum.wallet:1243: send tx failed: error: the transaction was rejected by network rules." errors, which is what happens now after about every 20 to 25 items.
@jiggytom has suggested that I look through the YouTube upload code, but it's in GO (which I don't know) so it's going a bit slow as I figure it out.  If you know that code and could give me some direction where to look, that would be great.

Might be encoding related. Can you find that part of the log that shows:
2018-06-27 21:32:10,346 INFO     lbrynet.daemon.Daemon:2147: Publish: {'claim_address': None, 'channel_id': u'', 'name': u'Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'license': u'None', u'language': u'en', u'title': u'test pub', 'version': '_0_1_0', u'nsfw': False, u'licenseUrl': u'', u'thumbnail': u''}}}, 'channel_name': None, 'bid': Decimal('0.00001'), 'file_path': u'xxxx', 'change_address': None}

as far as publishing in high volume, you'll either need to throttle it and wait for a new block/confirmation on a previous publish, or fill up enough addresses using https://lbryio.github.io/lbry/cli/#wallet_prefill_addresses.
The current wallet implementation starts to struggle with many addresses created, so many hold off mass publishing until the new one gets implemented.

@tzarebczan That was several days later.  These errors all happened on 6/22.

You can check the lbrynet.log1 (and so on) files for that info. Unless those were filled up also.

@tzarebczan This is what the full block looked like as generated by the program at that time (it's since been changed to generate shorter names):
{
"jsonrpc": "2.0",
"method":"publish",
"params": {
"name": "Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593",
"file_path": "D:\mp3\Saint, The\Publish to LBRY\Saint,The - 500702 - 04 - A Real Gone Guy  - 32-22 28m06s 6593.mp3",
"bid": 0.001,
"channel_name": "@OTR",
"metadata": {
"description": "Title: A Real Gone Guy\nAired: 1950-07-02\n",
"title": "The Saint - A Real Gone Guy",
"author": "",
"thumbnail": "http://www.42degreesdesign.com/images/thesaintotrshow.jpg",
"language": "en",
"license": "Public Domain",
"nsfw": false
}
}
}
All of the JSON sent would have be UTF-8 because of this call here:
new StringContent(publishRequest.Json, UTF8Encoding.UTF8, "application/json")

Here's the longer set of logs you asked for before and after the apparent name failure:
2018-06-22 18:35:02,220 INFO     lbrynet.daemon.Daemon:1141: Get version info: {"lbrynet_version": "0.20.2rc2", "platform": "Windows-10-10.0.17134", "os_system": "Windows", "python_version": "2.7.15", "os_release": "10", "lbryum_version": "3.2.3rc1", "ip": "<IP_ADDRESS>", "lbryschema_version": "0.0.16rc3", "processor": "Intel64 Family 6 Model 45 Stepping 6, GenuineIntel", "build": "rc"}
2018-06-22 18:37:45,286 INFO     lbrynet.daemon.Daemon:1141: Get version info: {"lbrynet_version": "0.20.2rc2", "platform": "Windows-10-10.0.17134", "os_system": "Windows", "python_version": "2.7.15", "os_release": "10", "lbryum_version": "3.2.3rc1", "ip": "<IP_ADDRESS>", "lbryschema_version": "0.0.16rc3", "processor": "Intel64 Family 6 Model 45 Stepping 6, GenuineIntel", "build": "rc"}
2018-06-22 18:41:37,203 INFO     lbrynet.daemon.Daemon:1141: Get version info: {"lbrynet_version": "0.20.2rc2", "platform": "Windows-10-10.0.17134", "os_system": "Windows", "python_version": "2.7.15", "os_release": "10", "lbryum_version": "3.2.3rc1", "ip": "<IP_ADDRESS>", "lbryschema_version": "0.0.16rc3", "processor": "Intel64 Family 6 Model 45 Stepping 6, GenuineIntel", "build": "rc"}
2018-06-22 19:21:15,862 INFO     lbrynet.daemon.Daemon:1141: Get version info: {"lbrynet_version": "0.20.2rc2", "platform": "Windows-10-10.0.17134", "os_system": "Windows", "python_version": "2.7.15", "os_release": "10", "lbryum_version": "3.2.3rc1", "ip": "<IP_ADDRESS>", "lbryschema_version": "0.0.16rc3", "processor": "Intel64 Family 6 Model 45 Stepping 6, GenuineIntel", "build": "rc"}
2018-06-22 19:35:38,727 INFO     lbrynet.daemon.Daemon:2147: Publish: {'claim_address': None, 'channel_id': None, 'name': u'Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'The Saint - A Real Gone Guy', u'license': u'Public Domain', u'author': u'', u'title': u'Title: A Real Gone Guy\nAired: 1950-07-02\n', u'language': u'en', 'version': '_0_1_0', u'nsfw': False, u'thumbnail': u'http://www.42degreesdesign.com/images/thesaintotrshow.jpg'}}}, 'channel_name': u'@OTR', 'bid': Decimal('0.001'), 'file_path': u'D:\\mp3\\Saint, The\\Publish to LBRY\\Saint,The - 500702 - 04 - A Real Gone Guy  - 32-22 28m06s 6593.mp3', 'change_address': None}

2018-06-22 19:35:38,746 INFO     lbrynet.daemon.Publisher:25: Starting publish for Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593
2018-06-22 19:35:38,971 INFO     lbrynet.core.Wallet:1203: Send claim: Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593 for 0.001: 080110011ae7010801129e01080410011a295469746c653a2041205265616c20476f6e65204775790a41697265643a20313935302d30372d30320a221b546865205361696e74202d2041205265616c20476f6e65204775792a00320d5075626c696320446f6d61696e38004a39687474703a2f2f7777772e34326465677265657364657369676e2e636f6d2f696d616765732f7468657361696e746f747273686f772e6a706752005a001a42080110011a305e0350f26e6ee7d63e3a6573103d16b7f4b0c03d5545788a63d0d6ba9d588b106305dfe9e9ffa11d87a70b2cdc0ea0ed220a617564696f2f6d706567
2018-06-22 19:35:39,278 INFO     root:205: using buckets: [u'a75806e7b248d1a1434d821d785ac5c2a74c06cb8210862284f9115cdab569f4:1']
2018-06-22 19:35:42,614 ERROR    lbryum:119: [lbryumx2.lbry.io] serving improperly sorted address histories

2018-06-22 19:35:43,105 INFO     lbrynet.daemon.Daemon:732: Success! Published to lbry://Saint-The-500702-04-A-Real-Gone-Guy-32-22-28m06s-6593 txid: 9fc3d56269adace93c42accfacd521e7a368da0070576188097ff0a38cec5e70 nout: 0
2018-06-22 19:35:43,114 WARNING  lbrynet.daemon.auth.server:211: error processing api request: Invalid name given to publish
traceback:   File "site-packages\twisted\internet\defer.py", line 1299, in _inlineCallbacks

  File "site-packages\lbrynet\daemon\Daemon.py", line 2039, in jsonrpc_publish

exceptions.Exception: Invalid name given to publish
2018-06-22 19:35:43,121 INFO     lbrynet.daemon.Daemon:2147: Publish: {'claim_address': None, 'channel_id': None, 'name': u'Saint-The-500618-02-A-Sonata-For-Slayers-32-22-27m57s-6553', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'The Saint - A Sonata For Slayers', u'license': u'Public Domain', u'author': u'', u'title': u'Title: A Sonata For Slayers\nAired: 1950-06-18\n', u'language': u'en', 'version': '_0_1_0', u'nsfw': False, u'thumbnail': u'http://www.42degreesdesign.com/images/thesaintotrshow.jpg'}}}, 'channel_name': u'@OTR', 'bid': Decimal('0.001'), 'file_path': u'D:\\mp3\\Saint, The\\Publish to LBRY\\Saint,The - 500618 - 02 - A Sonata For Slayers  - 32-22 27m57s 6553.mp3', 'change_address': None}
2018-06-22 19:35:43,141 INFO     lbrynet.daemon.Publisher:25: Starting publish for Saint-The-500618-02-A-Sonata-For-Slayers-32-22-27m57s-6553
2018-06-22 19:35:43,372 INFO     lbrynet.core.Wallet:1203: Send claim: Saint-The-500618-02-A-Sonata-For-Slayers-32-22-27m57s-6553 for 0.001: 080110011af101080112a801080410011a2e5469746c653a204120536f6e61746120466f7220536c61796572730a41697265643a20313935302d30362d31380a2220546865205361696e74202d204120536f6e61746120466f7220536c61796572732a00320d5075626c696320446f6d61696e38004a39687474703a2f2f7777772e34326465677265657364657369676e2e636f6d2f696d616765732f7468657361696e746f747273686f772e6a706752005a001a42080110011a30ad79a5a7a683dabcada0c22c276a7529d1c1b8f712bb9ca9be326782cce065cc31a8ec75d9f03d18ca744ff5a084e889220a617564696f2f6d706567
2018-06-22 19:35:43,677 INFO     root:205: using buckets: [u'90ed795cade649ad4238ff21ff1b73f0365c0c3f8a746606eaff29a8dd514d58:1']
2018-06-22 19:35:47,871 ERROR    lbryum:119: [lbryumx2.lbry.io] serving improperly sorted address histories

2018-06-22 19:35:48,137 INFO     lbrynet.daemon.Daemon:732: Success! Published to lbry://Saint-The-500618-02-A-Sonata-For-Slayers-32-22-27m57s-6553 txid: 34ffce54b3bd94d999ec6c775fd268012d9f202efc1b9388e2f352335a9bd493 nout: 0
2018-06-22 19:35:48,148 INFO     lbrynet.daemon.Daemon:2147: Publish: {'claim_address': None, 'channel_id': None, 'name': u'Saint-The-500903-13-Baseball-Murder-32-22-28m04s-6583', 'claim_dict': {'version': '_0_0_1', 'claimType': 'streamType', 'stream': {'version': '_0_0_1', 'metadata': {u'description': u'The Saint - Baseball Murder', u'license': u'Public Domain', u'author': u'', u'title': u'Title: Baseball Murder\nAired: 1950-09-03\n', u'language': u'en', 'version': '_0_1_0', u'nsfw': False, u'thumbnail': u'http://www.42degreesdesign.com/images/thesaintotrshow.jpg'}}}, 'channel_name': u'@OTR', 'bid': Decimal('0.001'), 'file_path': u'D:\\mp3\\Saint, The\\Publish to LBRY\\Saint,The - 500903 - 13 - Baseball Murder - 32-22 28m04s 6583.mp3', 'change_address': None}
2018-06-22 19:35:48,164 INFO     lbrynet.daemon.Publisher:25: Starting publish for Saint-The-500903-13-Baseball-Murder-32-22-28m04s-6583

@hackrush01 Can you update the api documentation with the valid characters?

@alyssaoc I will update them and make a PR soon to lbryum-refactor branch.

Added a PR #1428.
There seems to be no(practical) limitation on the length of the name of the claim
All these names resolve
PcjV6wu83Bmtu56aXDj5kO7dMtT1q8dCHObjlGlL1wR8v1hlVv8bvfgTWlNtMxIhjTzgkQ9n2d9N5YWiD1DP3qGKgFQfG8RRrcZE
PcjV6wu83Bmtu56aXDj5kO7dMtT1q8dCHObjlGlL1wR8v1hlVv8bvfgTWlNtMxIhjTzgkQ9n2d9N5YWiD1DP3qGKgFQfG8RRrcZEPcjV6wu83Bmtu56aXDj5kO7dMtT1q8dCHObjlGlL1wR8v1hlVv8bvfgTWlNtMxIhjTzgkQ9n2d9N5YWiD1DP3qGKgFQfG8RRrcZE
PcjV6wu83Bmtu56aXDj5kO7dMtT1q8dCHObjlGlL1wR8v1hlVv8bvfgTWlNtMxIhjTzgkQ9n2d9N5YWiD1DP3qGKgFQfG8RRrcZEPcjV6wu83Bmtu56aXDj5kO7dMtT1q8dCHObjlGlL1wR8v1hlVv8bvfgTWlNtMxIhjTzgkQ9n2d9N5YWiD1DP3qGKgFQfG8RRrcZEPcjV6wu83Bmtu56aXDj5kO7dMtT1q8dCHObjlGlL1wR8v1hlVv8bvfgTWlNtMxIhjTzgkQ9n2d9N5YWiD1DP3qGKgFQfG8RRrcZE
The issue with publish faced maybe due to the name being unicode. I think we accept only ascii names right now.


update upgrade doc

Coverage increased (+0.009%) to 48.454% when pulling a24c73da85f270ab179715cd378b7d96f366444f on mintao/update into 603893ac4f5ae7f80128e7280d325a704b9205ce on master.


Add visual indication of token flanking position when targeting

Addresses https://github.com/foundryvtt/pf2e/issues/4534.
This PR adds a scrolling floaty text "Flanking Position!" indicator on a token when that token targets another enemy token while possibly in flanking position. It's too big to embed, but I've uploaded a video demonstrating this feature. The indicator does not reveal whether or not the enemy token is actually flanked or is even flankable, in order to not give up possible metagame information (as discussed in the issue). Rather, this indicator shows that the targeting token could be in flanking position, if it is possible to flank the enemy token. The indicator respects reach and ally/enemy relationships.
The solution implemented is a bit different from that proposed in the issue. The issue suggested drawing a different target icon on the targeted token, with an additional hover-text note. Instead, this PR implements the indicator as temporary floating text on the targeting token. My thinking here is that while it's easy to figure out if a token is in a flanking position when the targeting is initiated, it's much more complicated to know whether that flanking position is maintained, since other tokens may move or die or experience conditions that prevent the original token from continuing to be in flanking position. Because of this, changing the targeting icon to represent flanking position either requires continually checking flanking position against many different changing circumstances or risking that the flanking-position targeting icon is displayed when no longer valid. Also, since it's the targeting token that is in position against the target, having the indicator appear over the targeting token seems to make more sense to me.
For any questions or anything, I'm on discord as JellyfishJail#3956.

I don't know if shark has made contact with you on discord, but I'll try to look into it later after the next release is in. I kinda feel bad letting this one sit for so long without feedback.
I'm unsure about using a token notification to do this, but its probably the simplest way. The only other thing that comes to mind is flashing a yellow glowy circle under your token and the flanking buddy, and a red glowy circle under the enemy circle, but that's very likely more involved to implement.

When it comes to visuals, I dislike the floaty text as that's rather vague. I don't think putting "Flanked" above the flanked token is bad if it happens over every token, even if it's not flankable.
However more elaborate solutions (like animated arrows or popups) feel a bit too much for something to be in the system by default. It would be great to have this sort of thing as a Hook though, so modules like PF2e Animations can make more elaborate and customizable animations for such notifications.

I am closing this PR because I believe it should be superseded by https://github.com/foundryvtt/pf2e/pull/9991, which addresses the same issue but using an on-demand highlight visual indicator.


Pending Contributions: Add the conversation Section to the Order Page

API

[x] Add new relation between Comment and Order

[x] Add migration to create new column

[x] Add comments resolvers to Order gql object

[x] Create "canComment" helper function for orders

Frontend

[ ] Add comments to GQL query
[ ] Add conversation component and threads to Order page
[ ] Conversation should be only visible to FromCollective, ToCollective, and ToCollectiveHost admins

Related / duplicate: https://github.com/opencollective/opencollective/issues/3266


Can't configure tracker integration

Maybe we're doing something wrong but we're getting 404 on the validation.
Note: I changed my API after this screenshot :)

Slightly different error here. On the browser console, I see all calls returns a 202, not a 404.
Those calls are not to a pivotal tracker address, but to the current app (the project monitor app itself).
When I look at the app logs, I see:
2015-04-23T07:27:38.371609+00:00 heroku[router]: at=info method=POST path="/projects/validate_tracker_project" host=<APP_NAME_HERE>.herokuapp.com request_id=8bb12914-048a-4895-9205-08afbc8cf9e4 fwd="<IP_ADDRESS>" dyno=web.1 connect=2ms service=75ms status=404 bytes=967
2015-04-23T07:27:38.295931+00:00 app[web.1]: Started POST "/projects/validate_tracker_project" for <IP_ADDRESS> at 2015-04-23 07:27:38 +0000
2015-04-23T07:27:38.367793+00:00 app[web.1]:
2015-04-23T07:27:38.367799+00:00 app[web.1]: ActiveRecord::RecordNotFound (Couldn't find Project without an ID):
2015-04-23T07:27:38.367801+00:00 app[web.1]:   app/controllers/projects_controller.rb:95:in `validate_tracker_project'
2015-04-23T07:27:38.367802+00:00 app[web.1]:   app/controllers/projects_controller.rb:121:in `scope_by_aggregate_project'
2015-04-23T07:27:38.367804+00:00 app[web.1]:
2015-04-23T07:27:38.367805+00:00 app[web.1]:

Seems it can't find the project.. but the request contains the id, and the project monitor db a project with that id.
One question: is it correct that the call is to a route in the same projectmonitor app instance? I see that the route is defined in routes.rb:
  post 'projects/validate_tracker_project'

but -being not familiar with ruby at all- I can't see in the code where the call to the actual pivotal tracker url is made... if I make a POST to http://pulse.pivotallabs.com/projects/validate_tracker_project (the URL in your screenshot) I just get a login page... my pivotal tracker login doesn't work.


Update README.md

Contributed by adding my name to the list.

This was easy to work on. Thank you.


Pipeline breaks because of puppeteer

Probably because of astro-diagram

Solved by installing puppeteer in demo package.
Should try import-meta-resolve for avoiding importing it alongside mermaid.


QFT as a circuit method

What is the expected behavior?
If we want to do a quantum fourier transform on a circuit we have to construct a QFT object and append it to the circuit. It would be much more natural and easier if we could just call a .qft method on the circuit with the appropriate arguments.
E.g. instead of
from qiskit import QuantumCircuit
from qiskit.aqua.components.qfts import Standard

circuit = QuantumCircuit(5)
qft = Standard(5)
qft_circuit = qft.construct_circuit()
circuit.append(qft.to_instruction(), list(range(5))

have
from qiskit import QuantumCircuit

circuit = QuantumCircuit(5)
circuit.qft(mode='standard')  # if no qubit indices are given do it over the full circuit
# if it should just be over a few certain qubits do
# circuit.qft([0, 1, 2], mode='standard')

This is not an immediate feature request, since the QFTs are also subject to change under the movement to circuits, but I think it would be a facilitating feature for algorithm construction and great to have.
What's other people's opinion about this?

I would like to understand more how the circuit will work/look for Ansatz before commenting further. I would have expected QFT to extend QuantumCircuit from what I understood was under discussion for Ansatz  - then the above would be circuit = QFT(mode='standard').
Otherwise if not, would qft be a standard method on QuantumCircuit - if its monkey patched on then I would want to avoid that at all costs.
We have a QFT circuit already in circuits. So sorting out what is a component and what is a circuit if they are the same thing is essence needs doing too.

I'm suggesting that we allow using the QFT as gate additionally to offering the QFT object.
I'm thinking of this the same way as the Y-rotation exists as RYGate and QuantumCircuit.ry. It seems more user-friendly to support both. And eventually the QFT is just a more elaborate gate :slightly_smiling_face:
The reason I'm opening this issue is to see how everybody feels about offering this syntax, I know it will take a while until we could think about implementing it.

For me it depends how .qft comes about. Monkey patched gates are a pain as you have to know they exist since they do not show up in IDEs for discovery. Directly added as methods for circuits that comprise some library of .qft, .phase_estimation etc then they are discoverable along with docstring help etc. I guess this ends up more of a question to Terra team framed like this though.
I am not sure its more user friendly to support both unless there are significant advantages/differences that are clear. Otherwise it may end up being more confusing as to why you would use one over the other etc.

I agree that monkey patched gates are annoying since they don't show up for IDE discovery.
But that's a bit a different topic since this is the case for all gates at the moment.

I am not sure its more user friendly to support both unless there are significant advantages/differences that are clear. Otherwise it may end up being more confusing as to why you would use one over the other etc.

One could raise the same points when talking about the standard gates. How is the QFT case different to the RY case in your opinion? Are you worrying that the missed IDE discovery is worse here because a .qft method would take more arguments than e.g. .ry?

Standard gates are be one thing (not keen on these either) but a circuit library that grows, where more function is added, seems less than desirable keep monkey patching things in.
Under what we had envisioned being done in #626 your above example was expected to be simpler more like
circuit = QuantumCircuit(5)
qft = Standard(5)
circuit.append(qft, list(range(5))

which maintains discoverability etc. (assuming all library objects we add are easily discoverable too)

The example you've posted is going to be possible soon, it's an upcoming feature of Terra that the registers can be overwritten. Along with QFT as QuantumCircuit we're there :+1:
But say we find a possibility to not do monkey-patching would that resolve your concerns? I'm also not saying everything in the circuit library should be appendable in this manner, but for the particular case of the QFT it seems handy :slightly_smiling_face:

To not blow up the circuit methods (which are not monkey patched anymore) this should probably not be done after all. Also, with the circuit library and the compose method adding the QFT is straightforward
circuit.compose(QFT(3), [0, 1, 2], inplace=True)

so no need for this anymore!


size mismatch issue

Hi, First of all thanks for making the repository public, I was going through your code seems to me there are some issues with the code for example. In line no. 35 of the DeMamba.py
_, _, c = sequence_output.shape

The output from CLIP is a 2D tensor consisting of (batch_size, logits)
Secondly in line no. 145-149 I am getting a shape mismatch error, it does not matter what inputs I choose
I have used an input of torch.randn(1, 16, 3, 224, 224) to check the model
Thank you, any kind of help would be greatly appreciated

Hi, we have modified the output of the CLIP, as referenced in https://github.com/chenhaoxing/DeMamba/blob/main/models/clip/model.py. The normal CLIP output is
x = self.ln_post(x[:, :1, :]),

which yields the CLS token of the ViT. To obtain spatial information, we have altered this to
x = self.ln_post(x[:, 1:, :]).


Can't select text for highlight or copy

For some reason we have user select set to none. Fixed in next release

Hi @nvcken, in the next release will be fix.

Okay guys, thanks


add volcengine endpoint for LLM

Description: Volc Engine MaaS serves as an enterprise-grade, large-model service platform designed for developers. You can visit its homepage at https://www.volcengine.com/docs/82379/1099455 for details. This change will facilitate developers to integrate quickly with the platform.
Issue: None
Dependencies: volcengine
Tag maintainer: @baskaryan
Twitter handle: @he1v3tica

PTAL @baskaryan

thanks @h3l!


Add ability to delete events

Subject: Add ability to delete events
Description:
There's no ability to delete an event.
Results:
Delete button
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/event/1708/milan-couchers-weekly-meeting
User: davideviolante (5019)

Dupe of #2988


[question] How to use sb-edit

I'm so confused as to how I can use this. The readme doesn't have clear instructions on how to use it. btw, I just want to get the leapord code of a scratch project that I can't upload onto scratch.

Bump, but for a different reason.
I found a scratchR repo and a Ubuntu ISO that runs scratchr on launch. HOWEVER, neither the java or the flashplayer shows anything, which is why I want to use sb-edit.

I'm marginally late, but sb-edit isn't a standalone program. It's a library for various manipulations of Scratch projects (which for now is only really used for sb3 -> leopard conversion).
You can use an external tool like sb-edit-playground to convert an sb3 project into Leopard locally. Skip the steps about npm link, since that's only for locally developing Leopard. Installing and then converting a project works like this:
cd /path/to/sb-edit-playground/
npm install
node index.js /path/to/your-project.sb3 leopard

You have to use a local web server to actually view the project:
cd /path/to/sb-edit-playground/ # if you aren't already there
cd ./out/leopard/
npx http-server -p 3001
# then navigate to http://localhost:3001/ in your web browser

Putting the output folder online somewhere should work too.


refactor!:  increase max gas limitation

What this PR does / why we need it?
This PR increase max gas limitation to 50 million.
What is the impact of this PR?
PR relation:

Ref https://github.com/godwokenrises/godwoken-tests/pull/319

CI Settings

CI Usage
Tip: Check the CI you want to run below, and then comment /run-ci.
CI Switch

[ ] Web3 Compatible Tests
[ ] OpenZeppelin tests
[ ] v3 Core Tests

CI Description

CI Name
Description

Web3 Compatible Test
Test the Web3 compatibility of Axon

v3 Core Test
Run the compatibility tests provided by Uniswap V3

OpenZeppelin tests
Run the compatibility tests provided by OpenZeppelin, including OCT 1-5 | 6-10 | 11 | 12-15 | 16-19

https://github.com/godwokenrises/godwoken-tests/pull/319
This PR has fix the test in a simple way.
I think it's should be discussed if this PR could be merged, because is might be a breaking change.

The root cause reason may be not the max gas limitation
@KaoImin


Minor documentation changes

@bors-servo r+
Thanks

:pushpin: Commit 90d4404 has been approved by emilio

:hourglass: Testing commit 90d4404 with merge d83e063...

:pushpin: Commit 90d4404 has been approved by emilio

:bulb: This pull request was already approved, no need to approve it again.

This pull request is currently being tested. If there's no response from the continuous integration service, you may use retry to trigger a build again.

:sunny: Test successful - status-travis


Timeline and beats callbacks

Hello! There is a little issue I wanna ask about. I'm subscribing on a Beat markers event, but because signals are fired only when _process in the game is called I'm getting a lag between an actual music beat and event. And that really troubles me. So the question - Is there some specific reason why signals are handled this way but not called right in the moment Fmod sends events?
Thanks!

Hi.
It was quite a while since that part was done so I'm not sure anymore.
I think the main reason was that we wanted the signals to be emitted by Godot main thread. As non-deferred signals are immediately calling the subscribers functions, if we were to call those signals from another thread, they would risk running at the same time as the main thread which could result in Data Race.
At the same time, we weren't knowledgeable enough about both Godot and the FMOD API so I guess we were too safe about that. But now that I checking that code again, I feel like it was unecessary.
You even have an option so Fmod triggers callback in a deferred way, just like you can defer Godot signals.
I guess I can make the change to emit the signals immediately instead of caching them for the next _process() call but it would be the responsibility of the user to be sure that the functions called by the signals are thread-safe.
Maybe I could add a parameter so you can set whether or not a signal is emitted immediately or not but that would overlap with the FMOD setting.
For reference:
https://fmod.com/resources/documentation-api?version=2.00&page=studio-guide.html#event-callbacks
Why is your opinion on that?

I guess I can make the change to emit the signals immediately instead of caching them
It would be great!

Maybe I could add a parameter so you can set whether or not a signal is emitted immediately or not but that would overlap with the FMOD setting.
I'm not sure it's really necessary and it can lead to a confusion. Probably it would be enough to mention it in readme and provide a link on Fmod docs. Or mb adding a little descriptions to FMOD_STUDIO_INIT_DEFERRED_CALLBACKS and FMOD_STUDIO_INIT_SYNCHRONOUS_UPDATE flags in gd script file