ADDED THE TRANSLATOR FUNCTION

ADDED A GOOD TRANSLATOR BUTTON ISSUE #815
https://github.com/user-attachments/assets/04451317-1bd5-440c-a3fe-dcc218f9a939

@sanjay-kv Good afternoon sir ,level 2 would be helpful it's working fine .Thank you

@sanjay-kv PLEASE HAVE A LOOK I HAVE FINISHED THE WORK KINDLY GIVE THE LABELS AND LEVEL 2 WOULD BE HELPFUL
THANK YOU

Your contributions are great can you become maintainer of this project, I will sponsor you as well. let me know @HS202022

Your contributions are great can you become maintainer of this project, I will sponsor you as well. let me know @HS202022

Sure will there be points for that?

Lets get connected on call. it would be easy.
let me know if you are free now @HS202022

Lets get connected on call. it would be easy.
let me know if you are free now @HS202022
Yeah fir sure

https://meet.google.com/ipx-boyw-vtx
@HS202022 join now


The documented defaults for "no-extraneous-dependencies" seem to be wrong

When I have this rule:
import/no-extraneous-dependencies: 2

...eslint complains if I try to import a devDependency in my code. Then, if I change my config to this:
import/no-extraneous-dependencies: [2, { devDependencies: true }]

...it stops complaining.
But the docs for this rule state that the devDependencies option defaults to true anyway, so I shouldn't have to set this explicitly. Either the docs are wrong or the defaults are wrong, or I've made a mistake somewhere.

I can confirm that the devDependencies option seems to default to false, whereas that documentation page says it defaults to true.

Yeah, this is confusing. The tests imply that it defaults to true as documented, but they could be bad tests... will need to look into it.
@jfmengels do you want to check this out?

Yeah, I meant to but I forgot to do it. Will try to look into it soon.

I can't reproduce this :confused:. Would someone be able to show me a repo where this fails, or create a failing test case (harder to do)?
Also, can you tell me the error message you got? Just want to make sure it was the dev dependency error message.

I can confirm this is the case. My eslintrc extends from airbnb-base (which disallows devDependencies imports) with the following simple content:
{
  "extends": "airbnb-base",
  "env": {
    "browser": true,
    "node": true,
    "mocha": true
  },
  "rules": {
    "no-console": 0,
    "semi": [2, "never"],
    "no-unexpected-multiline": 2
  }
}

With the following file:
const chai = require('chai')
const chaiAsPromised = require('chai-as-promised')

chai.use(chaiAsPromised)
chai.should()

It throws (as expected, due to airbnb-base's rule):
1:14  error  'chai' should be listed in the project's dependencies, not devDependencies
import/no-extraneous-dependencies
2:24  error  'chai-as-promised' should be listed in the project's dependencies, not devDependencies
import/no-extraneous-dependencies

However, adding "import/no-extraneous-dependencies": 2 does not resolve the error (this should override airbnb's rules, no?), while "import/no-extraneous-dependencies": [2, { "devDependencies": true }] does.

However, adding "import/no-extraneous-dependencies": 2 does not resolve the error (this should override airbnb's rules, no?), while "import/no-extraneous-dependencies": [2, { "devDependencies": true }] does.

This is exactly my experience. But I've looked into it further and I now think this might be a bug (or just surprising behaviour) in the way eslint handles overrides.
It looks like setting it to 2 doesn't reset the options, only the warning level.
You're right that explicitly setting the devDependencies fixes it:
rules:
  import/no-extraneous-dependencies: [2, { devDependencies: true }]

But I've just noticed that an empty object also fixes it:
rules:
  import/no-extraneous-dependencies: [2, {  }]

So it looks like you have to pass in an empty object to eslint in order to get it to reset the options to defaults, otherwise it just retains whatever options the rule has previously had set (and just applies your new severity level).

Wild. So that closes this issue, then? Sounds like it's just confusion when extending the Airbnb config?

yup. opened an issue here; please go and upvote it!

My inline overrides have stopped working as well:
/* eslint import/no-extraneous-dependencies: ["error", {"devDependencies": true}] */

Any suggestions?


Fix hyperv support

Vhds no longer work with gen 2 VMs and are hence restricted to gen 1 VMs which only support bios emulation.
Need to either get diskpart to output a vhdx or get hyperv to convert the vhd automatically.

Nevermind.
While the new vm action doesn't allow using a vhd as an existing image, selecting attach later and then going into settings, adding a hard drive to the SCSI controller, manually entering the file name despite it not appearing since the open dialog is locked to vhdx and avhdx files and then finally changing the boot order does allow it to be added.
Might still be worth switching to vhdx though to avoid this.


Add documentation

After a few weeks‘ of work, we have a working repository, and now: a readme!

Going to leave this PR open for a few more days to see if I can get another review pass with the new changes. Once this gets merged I'll release a 0.1.0 beta version of SafeDI!

I'm going to merge this, but I am still quite open to feedback on both this documentation and the API! I'll be pushing a beta 0.1.0 tag release of this repo shortly, but since we're still in beta it's a good time to provide API feedback!
One bit of feedback I've received offline from a couple folk is that much of the content in this README would be best split out into wiki docs, and the README should be refocused on more of a Quickstart guide (with clear code examples pulled from the sample project) + linking to the rest of the wiki. This is great feedback, and I agree with it, but in the spirit of shipping I'm going to merge this as-is and take a future action item to rework this.


[FR] Add Stylelint

See #11 for request to add Stylelint in a new PR
This would also help with automated readability and dbarenholz friendliness.

After some changes we did to the CSS, Stylelint may not be needed.


teetty passthrough SIGWINCH support

It would be really awesome if teetty would passthrough the SIGWINCH signal to the inferior pty. i.e. capture the SIGWINCH signal sent to teetty and send it to the inferior process of the teetty pty. Or perhaps this is the job of another utility to proxy signals.
Even tcl/expect does not support this, to my knowledge.
http://www.rkoucha.fr/tech_corner/sigwinch.html
Example of resizing inside and out of teetty:
https://asciinema.org/a/548055

It is actually trying to do that but for some reason failing. This is a bug I haven't been able to fix yet.
https://github.com/mitsuhiko/teetty/blob/99440fc98aa934c2b52d2a9f07294b3a1f08278d/src/spawn.rs#L162-L179

If someone wants to debug this. Here is what I tried to do so far:
This Python script prints out on window size changes the current terminal size:
import time
import struct, fcntl, termios, signal, sys

def sigwinch_passthrough (sig, data):
    s = struct.pack("HHHH", 0, 0, 0, 0)
    a = struct.unpack('hhhh', fcntl.ioctl(sys.stdout.fileno(),
        termios.TIOCGWINSZ , s))
    print(a[0], a[1])

signal.signal(signal.SIGWINCH, sigwinch_passthrough)

while True:
    time.sleep(1)

When run in teetty it always prints out the initial terminal size. The get_winsize call however in the sigwinch_passthrough prints out the right information. Likewise the wet_winsize call to the pty also does not create an error and forwards the right window size. Likewise I already verified that killpg is going to the right process. Without it Python does not see the signal arrive.
So somehow the TIOCGWINSZ ioctl write to the terminal has no effect.

Well that's because you're supposed to write to TIOCSWINSZ not TIOCGWINSZ. Fixed that now.

Thanks. I'm impressed at how fast you fixed that.
This is SIGWINCH being correctly handled in teetty:
https://asciinema.org/a/548225


Format Android manifest file. Fix some Eclipse warnings in latest SDK.

Formats Android manifest file and removes some warnings in the latest SDK.

Thanks for the pull request! However, this repository is outdated and no longer the canonical source. I've updated the README.md to explain where the main projects now live.


Adds support for selectedIcon

Adds support to choose a different icon when a node is selected. I left out the files copied by grunt in the PR but I can add them if you'd like me to.

Great contribution / idea, thanks.
It's been a long time since someone has actually taken the time to present a complete PR, including doc, test etc.

I just noticed one problem...the PR is set to merge into master, it needs to merge into develop so it can run through the standard git-flow release cycle.
Any chance you could update/redo so that I can merge into the correct branch.  I'm not sure I can change this configuration via GitHub.  I could pull locally and merge myself but then I guess you would not be credited with the contribution.
Thanks.

Just opened a new PR on the develop branch. Thanks for the heads up.


disable 'pull' option for filesync

'pull' is not a valid action for FileSync V1

Accidently duplicated in 2289


Population and group size of GA.

I run the tuning process of SiamFC with OTB-2015 on the cloud by 8 GPUs, but it takes a long time to get the results.
The population and group size of GA in tune_gune are both set to 100, the population size seems quite bigger, so I am thinking to reduce it, is that possible? Do you test the tuning process of SiamFC using GA
with small population size?

I run the tuning process of SiamFC with OTB-2015 on the cloud by 8 GPUs, but it takes a long time to get the results.
The population and group size of GA in tune_gune are both set to 100, the population size seems quite bigger, so I am thinking to reduce it, is that possible? Do you test the tuning process of SiamFC using GA
with small population size?

Yes, it takes a long time to tune hyper-parameters.
The total hyperparametric numbers needs to reach a certain scale even with a small population size. It takes about one day with 8 GPUs.
Try TPE for better results.

I run the tuning process of SiamFC with OTB-2015 on the cloud by 8 GPUs, but it takes a long time to get the results.
The population and group size of GA in tune_gune are both set to 100, the population size seems quite bigger, so I am thinking to reduce it, is that possible? Do you test the tuning process of SiamFC using GA
with small population size?

Yes, it takes a long time to tune hyper-parameters.
The total hyperparametric numbers needs to reach a certain scale even with a small population size. It takes about one day with 8 GPUs.
Try TPE for better results.

Thanks, the TPE seems not working after you fixing TAB-SPACE bugs of test_siamfc.py, and comment in code said the GA is faster than TPE(not faster enough, I prefer to use TPE ). Thus I run GA instead.  I got error messages like this:
2019-07-15 05:55:28,916	WARNING experiment.py:30 -- trial_resourcesis deprecated. Please useresources_per_trial. trial_resources` will be removed in future versions of Ray.
2019-07-15 05:55:28,916	INFO tune.py:139 -- Did not find checkpoint file in ./TPE_results/zp_tune.
2019-07-15 05:55:28,916	INFO tune.py:145 -- Starting a new experiment.
== Status ==
Using AsyncHyperBand: num_stopped=0
Bracket: Iter 180.000: None | Iter 60.000: None | Iter 20.000: None
Bracket: Iter 180.000: None | Iter 60.000: None
Bracket: Iter 180.000: None
Resources requested: 0/4 CPUs, 0/1 GPUs
Memory usage on this node: 6.7/16.7 GB
2019-07-15 05:55:29,000	WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
== Status ==
Using AsyncHyperBand: num_stopped=0
Bracket: Iter 180.000: None | Iter 60.000: None | Iter 20.000: None
Bracket: Iter 180.000: None | Iter 60.000: None
Bracket: Iter 180.000: None
Resources requested: 1/4 CPUs, 0.5/1 GPUs
Memory usage on this node: 6.8/16.7 GB
Result logdir: ./TPE_results/zp_tune
PENDING trials:

fitness_2_scale_lr=0.5674,scale_penalty=0.9596,scale_step=1.0614,w_influence=0.3149:	PENDING
fitness_3_scale_lr=0.5008,scale_penalty=0.9529,scale_step=1.1539,w_influence=0.2413:	PENDING
fitness_4_scale_lr=0.6948,scale_penalty=0.9551,scale_step=1.011,w_influence=0.4641:	PENDING
fitness_5_scale_lr=0.6827,scale_penalty=0.9836,scale_step=1.0539,w_influence=0.6642:	PENDING
RUNNING trials:
fitness_1_scale_lr=0.2358,scale_penalty=0.9937,scale_step=1.1995,w_influence=0.5447:	RUNNING

2019-07-15 05:55:29,109	WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
2019-07-15 05:55:29,346	WARNING logger.py:27 -- Couldn't import TensorFlow - disabling TensorBoard logging.
2019-07-15 05:55:29,396	WARNING logger.py:27 -- Couldn't import TensorFlow - disabling TensorBoard logging.
2019-07-15 05:55:29,997	ERROR worker.py:1632 -- Failed to unpickle actor class 'WrappedFunc' for actor ID 4081809b3f48f44d15f26536b32befdb77815c5f. Traceback:
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/function_manager.py", line 632, in fetch_and_register_actor
unpickled_class = pickle.loads(pickled_class)
ModuleNotFoundError: No module named 'tracker'
2019-07-15 05:55:29,998	ERROR worker.py:1632 -- Failed to unpickle actor class 'WrappedFunc' for actor ID 7e05f09aa98b7d34320bcf1366eed7cd1bd0e8f1. Traceback:
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/function_manager.py", line 632, in fetch_and_register_actor
unpickled_class = pickle.loads(pickled_class)
ModuleNotFoundError: No module named 'tracker'
2019-07-15 05:55:29,999	ERROR trial_runner.py:413 -- Error processing event.
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/trial_runner.py", line 378, in _process_events
result = self.trial_executor.fetch_result(trial)
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/ray_trial_executor.py", line 228, in fetch_result
result = ray.get(trial_future[0])
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/worker.py", line 2132, in get
raise value
ray.worker.RayTaskError: ray_worker (pid=28562, host=bo-Surface-Book-2)
Exception: The actor with name WrappedFunc failed to be imported, and so cannot execute this method
2019-07-15 05:55:30,037	WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
2019-07-15 05:55:30,129	ERROR trial_runner.py:413 -- Error processing event.
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/trial_runner.py", line 378, in _process_events
result = self.trial_executor.fetch_result(trial)
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/ray_trial_executor.py", line 228, in fetch_result
result = ray.get(trial_future[0])
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/worker.py", line 2132, in get
raise value
ray.worker.RayTaskError: ray_worker (pid=28563, host=bo-Surface-Book-2)
Exception: The actor with name WrappedFunc failed to be imported, and so cannot execute this method
2019-07-15 05:55:30,173	WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
`
Any suggestions of this?

ModuleNotFoundError: No module named 'tracker'

Rerun the code for several times. Sometimes it reports No module named tracker or No module named model  for unknowen reason.

I run the tuning process of SiamFC with OTB-2015 on the cloud by 8 GPUs, but it takes a long time to get the results.
The population and group size of GA in tune_gune are both set to 100, the population size seems quite bigger, so I am thinking to reduce it, is that possible? Do you test the tuning process of SiamFC using GA
with small population size?

Yes, it takes a long time to tune hyper-parameters.
The total hyperparametric numbers needs to reach a certain scale even with a small population size. It takes about one day with 8 GPUs.
Try TPE for better results.

Thanks, the TPE seems not working after you fixing TAB-SPACE bugs of test_siamfc.py, and comment in code said the GA is faster than TPE(not faster enough, I prefer to use TPE ). Thus I run GA instead. I got error messages like this:
2019-07-15 05:55:28,916 WARNING experiment.py:30 -- trial_resourcesis deprecated. Please useresources_per_trial. trial_resources` will be removed in future versions of Ray.
2019-07-15 05:55:28,916 INFO tune.py:139 -- Did not find checkpoint file in ./TPE_results/zp_tune.
2019-07-15 05:55:28,916 INFO tune.py:145 -- Starting a new experiment.
== Status ==
Using AsyncHyperBand: num_stopped=0
Bracket: Iter 180.000: None | Iter 60.000: None | Iter 20.000: None
Bracket: Iter 180.000: None | Iter 60.000: None
Bracket: Iter 180.000: None
Resources requested: 0/4 CPUs, 0/1 GPUs
Memory usage on this node: 6.7/16.7 GB
2019-07-15 05:55:29,000 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
== Status ==
Using AsyncHyperBand: num_stopped=0
Bracket: Iter 180.000: None | Iter 60.000: None | Iter 20.000: None
Bracket: Iter 180.000: None | Iter 60.000: None
Bracket: Iter 180.000: None
Resources requested: 1/4 CPUs, 0.5/1 GPUs
Memory usage on this node: 6.8/16.7 GB
Result logdir: ./TPE_results/zp_tune
PENDING trials:
* fitness_2_scale_lr=0.5674,scale_penalty=0.9596,scale_step=1.0614,w_influence=0.3149:	PENDING

* fitness_3_scale_lr=0.5008,scale_penalty=0.9529,scale_step=1.1539,w_influence=0.2413:	PENDING

* fitness_4_scale_lr=0.6948,scale_penalty=0.9551,scale_step=1.011,w_influence=0.4641:	PENDING

* fitness_5_scale_lr=0.6827,scale_penalty=0.9836,scale_step=1.0539,w_influence=0.6642:	PENDING
  RUNNING trials:

* fitness_1_scale_lr=0.2358,scale_penalty=0.9937,scale_step=1.1995,w_influence=0.5447:	RUNNING

2019-07-15 05:55:29,109 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
2019-07-15 05:55:29,346 WARNING logger.py:27 -- Couldn't import TensorFlow - disabling TensorBoard logging.
2019-07-15 05:55:29,396 WARNING logger.py:27 -- Couldn't import TensorFlow - disabling TensorBoard logging.
2019-07-15 05:55:29,997 ERROR worker.py:1632 -- Failed to unpickle actor class 'WrappedFunc' for actor ID 4081809b3f48f44d15f26536b32befdb77815c5f. Traceback:
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/function_manager.py", line 632, in fetch_and_register_actor
unpickled_class = pickle.loads(pickled_class)
ModuleNotFoundError: No module named 'tracker'
2019-07-15 05:55:29,998 ERROR worker.py:1632 -- Failed to unpickle actor class 'WrappedFunc' for actor ID 7e05f09aa98b7d34320bcf1366eed7cd1bd0e8f1. Traceback:
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/function_manager.py", line 632, in fetch_and_register_actor
unpickled_class = pickle.loads(pickled_class)
ModuleNotFoundError: No module named 'tracker'
2019-07-15 05:55:29,999 ERROR trial_runner.py:413 -- Error processing event.
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/trial_runner.py", line 378, in _process_events
result = self.trial_executor.fetch_result(trial)
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/ray_trial_executor.py", line 228, in fetch_result
result = ray.get(trial_future[0])
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/worker.py", line 2132, in get
raise value
ray.worker.RayTaskError: ray_worker (pid=28562, host=bo-Surface-Book-2)
Exception: The actor with name WrappedFunc failed to be imported, and so cannot execute this method
2019-07-15 05:55:30,037 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
2019-07-15 05:55:30,129 ERROR trial_runner.py:413 -- Error processing event.
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/trial_runner.py", line 378, in _process_events
result = self.trial_executor.fetch_result(trial)
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/ray_trial_executor.py", line 228, in fetch_result
result = ray.get(trial_future[0])
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/worker.py", line 2132, in get
raise value
ray.worker.RayTaskError: ray_worker (pid=28563, host=bo-Surface-Book-2)
Exception: The actor with name WrappedFunc failed to be imported, and so cannot execute this method
2019-07-15 05:55:30,173 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
`
Any suggestions of this?

Rerun the code for several times. Sometimes it reports No module named tracker or No module named model for unknowen reason.

I run the tuning process of SiamFC with OTB-2015 on the cloud by 8 GPUs, but it takes a long time to get the results.
The population and group size of GA in tune_gune are both set to 100, the population size seems quite bigger, so I am thinking to reduce it, is that possible? Do you test the tuning process of SiamFC using GA
with small population size?

Yes, it takes a long time to tune hyper-parameters.
The total hyperparametric numbers needs to reach a certain scale even with a small population size. It takes about one day with 8 GPUs.
Try TPE for better results.

Thanks, the TPE seems not working after you fixing TAB-SPACE bugs of test_siamfc.py, and comment in code said the GA is faster than TPE(not faster enough, I prefer to use TPE ). Thus I run GA instead. I got error messages like this:
2019-07-15 05:55:28,916 WARNING experiment.py:30 -- trial_resourcesis deprecated. Please useresources_per_trial. trial_resources` will be removed in future versions of Ray.
2019-07-15 05:55:28,916 INFO tune.py:139 -- Did not find checkpoint file in ./TPE_results/zp_tune.
2019-07-15 05:55:28,916 INFO tune.py:145 -- Starting a new experiment.
== Status ==
Using AsyncHyperBand: num_stopped=0
Bracket: Iter 180.000: None | Iter 60.000: None | Iter 20.000: None
Bracket: Iter 180.000: None | Iter 60.000: None
Bracket: Iter 180.000: None
Resources requested: 0/4 CPUs, 0/1 GPUs
Memory usage on this node: 6.7/16.7 GB
2019-07-15 05:55:29,000 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
== Status ==
Using AsyncHyperBand: num_stopped=0
Bracket: Iter 180.000: None | Iter 60.000: None | Iter 20.000: None
Bracket: Iter 180.000: None | Iter 60.000: None
Bracket: Iter 180.000: None
Resources requested: 1/4 CPUs, 0.5/1 GPUs
Memory usage on this node: 6.8/16.7 GB
Result logdir: ./TPE_results/zp_tune
PENDING trials:
* fitness_2_scale_lr=0.5674,scale_penalty=0.9596,scale_step=1.0614,w_influence=0.3149:	PENDING

* fitness_3_scale_lr=0.5008,scale_penalty=0.9529,scale_step=1.1539,w_influence=0.2413:	PENDING

* fitness_4_scale_lr=0.6948,scale_penalty=0.9551,scale_step=1.011,w_influence=0.4641:	PENDING

* fitness_5_scale_lr=0.6827,scale_penalty=0.9836,scale_step=1.0539,w_influence=0.6642:	PENDING
  RUNNING trials:

* fitness_1_scale_lr=0.2358,scale_penalty=0.9937,scale_step=1.1995,w_influence=0.5447:	RUNNING

2019-07-15 05:55:29,109 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
2019-07-15 05:55:29,346 WARNING logger.py:27 -- Couldn't import TensorFlow - disabling TensorBoard logging.
2019-07-15 05:55:29,396 WARNING logger.py:27 -- Couldn't import TensorFlow - disabling TensorBoard logging.
2019-07-15 05:55:29,997 ERROR worker.py:1632 -- Failed to unpickle actor class 'WrappedFunc' for actor ID 4081809b3f48f44d15f26536b32befdb77815c5f. Traceback:
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/function_manager.py", line 632, in fetch_and_register_actor
unpickled_class = pickle.loads(pickled_class)
ModuleNotFoundError: No module named 'tracker'
2019-07-15 05:55:29,998 ERROR worker.py:1632 -- Failed to unpickle actor class 'WrappedFunc' for actor ID 7e05f09aa98b7d34320bcf1366eed7cd1bd0e8f1. Traceback:
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/function_manager.py", line 632, in fetch_and_register_actor
unpickled_class = pickle.loads(pickled_class)
ModuleNotFoundError: No module named 'tracker'
2019-07-15 05:55:29,999 ERROR trial_runner.py:413 -- Error processing event.
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/trial_runner.py", line 378, in _process_events
result = self.trial_executor.fetch_result(trial)
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/ray_trial_executor.py", line 228, in fetch_result
result = ray.get(trial_future[0])
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/worker.py", line 2132, in get
raise value
ray.worker.RayTaskError: ray_worker (pid=28562, host=bo-Surface-Book-2)
Exception: The actor with name WrappedFunc failed to be imported, and so cannot execute this method
2019-07-15 05:55:30,037 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
2019-07-15 05:55:30,129 ERROR trial_runner.py:413 -- Error processing event.
Traceback (most recent call last):
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/trial_runner.py", line 378, in _process_events
result = self.trial_executor.fetch_result(trial)
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/tune/ray_trial_executor.py", line 228, in fetch_result
result = ray.get(trial_future[0])
File "/home/bo/anaconda3/envs/siamDW/lib/python3.6/site-packages/ray/worker.py", line 2132, in get
raise value
ray.worker.RayTaskError: ray_worker (pid=28563, host=bo-Surface-Book-2)
Exception: The actor with name WrappedFunc failed to be imported, and so cannot execute this method
2019-07-15 05:55:30,173 WARNING logger.py:105 -- Could not instantiate <class 'ray.tune.logger._TFLogger'> - skipping.
`
Any suggestions of this?

Rerun the code for several times. Sometimes it reports No module named tracker or No module named model for unknowen reason.

Thanks.


Add script that allows user to generate comparison plots for different filters/methods.

Add script that allows the user to generate comparison plots for different filters/methods, update style.css for links, update font-size in app.py
Files changed: created comparison_app.py, update style.css, update app.py
Future work: Link app.py and comparison_app.py using dcc links, update dash to its latest version and make web-app compatible with it.
This is the current interface:

Does it work if the user doesn't want to compare? Like if only one option is selected.

Does it work if the user doesn't want to compare? Like if only one option is selected.

Yes, it will work, but it will also show the plots and elements for the default value there is on the other dropdown. I have created comparison_app.py separately and I am trying to link this to app.py(a multi-page web-app). Then the user will be able to switch between normal and comparison mode according to his requirement. See here- https://dash.plot.ly/urls

Oh, cool. Keep working on it.


[Discussion] Open Source Sync Server?

Been using Insomnia for a few months and since the project is now open source do you have a plan to give users the option to host their own sync server?
I'm sorry if I'm rude because this is basically the project revenue source, just thought it might worth asking.
Cheers.

I'd like to hear what the rest of the community thinks about this. I'm certainly open to discussing the topic.
At the moment, the sync server codebase is still in flux and not designed to be hosted easily. It would need a lot of work to make it "user-friendly", not to mention figure out a way to issue updates.
I'm not that worried about how it will affect revenue. There are plenty of companies (eg. Sentry and GitLab) that use the same open-source model.

I think a self-hosted sync server would be beyond awesome, but then again, if it's something that would require a significant effort from the dev's side then I think it should be a very low-priority, nice-to-have thing for the future.

I think we should work on making Insomnia better for everyone without harming the revenue of the people who gave this all to us for free. Makes no sense to me.

I'm closing this for now but feel free to keep leaving comments.

By adding an option to self-host the Insomnia Sync servers, more people would use this instead of proprietary alternatives. And if they would like extended support and things like that, then they can use the offical Insomia Sync servers. Sentry did it really well without affecting the revenue of the company.

You could release that code for now without the billing part and people will probably make pull requests that fix most problems

That's the hard part though.. 😢

We doesn't need it to be perfect when its released. If its open-source that means we can make our patches if we find some problems. We just need an option for the client to use a custom server and a working version of the server(as i said, it doesn't have to be perfect, it just needs to work for now). I think large enterprises and people who like self-hosting would immediately start fixing bugs, and some of them maybe even give donations.

I am working on an OSS self-hosted project right now with a small team of people, and this is the REST client we  like use, and it being not self-hostable is the only problem we have with it.

What prevents other people from writing their own sync server without depending @gschier server code?
In the sense that no one can be forced to release their code as open source, and makes less sense when that code is their way of revenue. People can just write their own sync servers from scratch right?

As this project is open-source, reverse engineering a sync server would probably be easy for people that know how to do it. But still, at least having a full documentation for the api or a small python test server would help people make their own servers for the project.

I agree. It would be great if you could give an API spec so the community can build their own custom servers.
Great project btw :+1:

Hey @gschier any updates on this? Really looking forward to this feature!

Hi @gschier, I'd also appreciate sync server being open source, or at least a documentation of the API so we can write our own server implementations. And as I see the history of this issue, I think there are a lot of people who'd appreciate this as well.

Would anyone be interested in this, either by creating a plugin with the same functionalities as the official synchronization, or by reverse engineering the code in Insomnia which communicates with the sync server and writing our own implementation?

I would be interested to pick this up @jirian. Let's connect?
On Sun, 11 Oct 2020 at 4:27 AM, jirian<EMAIL_ADDRESS>wrote:

Would anyone be interested in this, either by creating a plugin with the
same functionalities as the official synchronization, or by reverse
engineering the code in Insomnia which communicates with the sync server
and writing our own implementation?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Kong/insomnia/issues/190#issuecomment-706622605, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAWFLNRGDO4BSNI7ZVOBG3SKDRFXANCNFSM4DLDAALA
.

--
Sent from Gmail Mobile

That'd be great. Which way of communication do you prefer? We can use email, but I'd actually say it'd be easier to just use GitHub issues in a new repo dedicated to the project (e.g. https://github.com/jirian/insomnia-server - it's almost empty so far).

@gschier @xMate420x @rohinrohin @rohinwork @jirian Any updates on this? Was anyone able to reverse engineer this?

https://insomnia.rest/plugins/insomnia-plugin-gitlab
Meanwhile gitlab or other git cloud servers can be used for syncing. (Credits to Dignat )

@gschier Can you provide an updated answer to the request? We don't want the full implementation to be open sourced if that's impossible to do but at least one documentation page that we can use to implement an alternative version of the backend. Now, if anyone is trying to reverse engineer the sync server would have to modify the Insomnia client too since it is making requests to the particular Insomnia server which is not open sourced.

I'm closing this for now but feel free to keep leaving comments.
Can you open it again, please?


311 Add a database library

Purpose:
This pull request will implement a light SQLite database library.

Codecov Report

Merging #312 (f59804a) into master (80ef243) will decrease coverage by 0.51%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #312      +/-   ##
==========================================
- Coverage   22.69%   22.18%   -0.52%
==========================================
  Files         127      128       +1
  Lines        2824     2889      +65
  Branches     1578     1622      +44
==========================================
  Hits          641      641
- Misses       1677     1742      +65
  Partials      506      506

Impacted Files
Coverage Δ

libs/Database/Database.cpp
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Error pops out when repairing the game

System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'from')
   at System.Net.Http.Headers.RangeItemHeaderValue..ctor(Nullable`1 from, Nullable`1 to)
   at System.Net.Http.Headers.RangeHeaderValue..ctor(Nullable`1 from, Nullable`1 to)
   at Hi3Helper.Http.Http.GetSession(SessionAttribute Session) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Session.cs:line 20
   at Hi3Helper.Http.Http.RetryableTaskContainer(SessionAttribute Session, Boolean IsMultisession) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Thread.cs:line 70
   at Hi3Helper.Http.Http.StartRetryableTask(SessionAttribute Session, Boolean IsMultisession) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Thread.cs:line 84
   at Hi3Helper.Http.Http.TryAwaitOrDisposeStreamWhileFail(Task InnerTask, SessionAttribute Session) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Thread.cs:line 115
 ---> System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'from')
   at System.Net.Http.Headers.RangeItemHeaderValue..ctor(Nullable`1 from, Nullable`1 to)
   at System.Net.Http.Headers.RangeHeaderValue..ctor(Nullable`1 from, Nullable`1 to)
   at Hi3Helper.Http.Http.GetSession(SessionAttribute Session) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Session.cs:line 20
   at Hi3Helper.Http.Http.RetryableTaskContainer(SessionAttribute Session, Boolean IsMultisession) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Thread.cs:line 70
   at Hi3Helper.Http.Http.StartRetryableTask(SessionAttribute Session, Boolean IsMultisession) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Thread.cs:line 84
   at Hi3Helper.Http.Http.TryAwaitOrDisposeStreamWhileFail(Task InnerTask, SessionAttribute Session) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Thread.cs:line 115
   --- End of inner exception stack trace ---
   at Hi3Helper.Http.Http.TryAwaitOrDisposeStreamWhileFail(Task InnerTask, SessionAttribute Session) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Class\Thread.cs:line 128
   at Hi3Helper.Http.Http.DownloadStream(String URL, Stream OutStream, CancellationToken Token, Int64 Start, Nullable`1 End) in C:\myGit\CollapseLauncher-fix20220825\Hi3HelperCore.Http\Http.cs:line 49
   at CollapseLauncher.Pages.RepairPage.RepairBlockFiles(FilePropertiesRemote input) in C:\myGit\CollapseLauncher-fix20220825\CollapseLauncher\Classes\RepairManagement\DataRepair.cs:line 158
   at CollapseLauncher.Pages.RepairPage.CategorizeRepairAction() in C:\myGit\CollapseLauncher-fix20220825\CollapseLauncher\Classes\RepairManagement\DataRepair.cs:line 64
   at CollapseLauncher.Pages.RepairPage.StartGameRepair(Object sender, RoutedEventArgs e) in C:\myGit\CollapseLauncher-fix20220825\CollapseLauncher\Classes\RepairManagement\DataRepair.cs:line 31```

Seems like this is an issue with the Hi3Helper.Http submodule. I will look into that later because I'm currently away now and will be back on Sept 11th.

I just investigated the issue and turns out, the issue was caused by the EndOffset by this piece of code in Hi3Helper.Http submodule:
https://github.com/neon-nyan/Hi3Helper.Http/blob/5e9e8d2d583b78db3127a0934fa7b18ccd14b623/Class/Session.cs#L20
The EndOffset is not checkedn while getting set to -1 and leave it as is. Instead, it will give the value -2 and causing invalid range.

Anyway, I'm planning to make a hotfix for this later or as soon as possible so,... wait for it while I'm trying to make a fix for this 😃

Update
This issue should've been fixed on the new <IP_ADDRESS>-Hotfix update.
Please update your launcher to fix this issue and you can consider close this issue if you feel that this issue has been solved.
Once again, thank you for reporting this.

Where is the <IP_ADDRESS>-Hotfix update? I would like to try it out
Couldn't find it on Release

@DarkXonline the update on GitHub page hasn't been published.
You can do update inside of the launcher.
Go to App Settings -> Scroll down and click Check Update button

@DarkXonline the update on GitHub page hasn't been published. You can do update inside of the launcher.
Go to App Settings menu -> Scroll down and click Check Update button

I see, I will update now :D


Preview Pane doesn't use custom CSS

Describe the bug
The Preview Pane doesn't use custom CSS (nor custom template).
Duplicate ?
Seems close enough to #1599 except I don't know or use Emotion, only pure CSS.
To Reproduce

Create a project (existing Eleventy blog in my case)
Add config for your collections (simple blog articles, nothing tricky)
In your admin/index.html register your CS in a script block. I tried followings, separately and together:

<script>
  CMS.registerPreviewStyle('https://my-blog.com/css/my-blog.css');
  CMS.registerPreviewStyle('/css/my-blog.css'); /* relative path on generated site */
  CMS.registerPreviewStyle('/src/css/my-blog.css'); /* relative path on repository */

  var PostPreview = createClass({
    render: function() {
      var entry = this.props.entry;
      var image = entry.getIn(['data', 'image']);
      var bg = this.props.getAsset(image);
      return h('div', {"className": "text"}, this.props.widgetFor('body'));
    }
  }); /* simple preview with only the body, easy to see the difference */

  CMS.registerPreviewTemplate("posts", PostPreview);
</script>

Deploy your site and reload Netlify CMS after cleaning cache.

Expected behavior
When editing an article/element of a collection, the preview pane on the right use your custom CSS.
Mine have dark background and light text color so easy to see if working or not.
Screenshots

Applicable Versions:

Netlify CMS version: 2.10.84
Git provider: GitLab
OS: Debian stable
Browser version Firefox Developer Edition 85.0b9, Google Chrome 87.0.4280.141

CMS configuration
backend:
  name: gitlab
  repo: me/my-blog
  auth_type: implicit
  app_id: ???

publish_mode: editorial_workflow

media_folder: "src/img"
public_folder: "/img"

site_url: https://my-blog.com/
display_url: https://my-blog.com/

show_preview_links: false

locale: 'fr'

collections:
  - name: "posts"
    label: "Articles"
    folder: "src/posts"
    create: true
    slug: "{{slug}}"
    fields:
      - {label: "titre", name: "title", widget: "string"}
      - {label: "date de publication", name: "date", widget: "datetime"}
      - {label: "description", name: "description", widget: "text"}
      - {label: "image", name: "image", widget: "image", required: false}
      - {label: "description de l'image", name: "image_description", widget: "text", required: false}
      - {label: "contenu", name: "body", widget: "markdown"}

I finally fixed this by putting registerPreviewStyle and the registerLocale stuff in different <script> blocs, as following:
    <script<EMAIL_ADDRESS>    <script>CMS.registerPreviewStyle('https://a-la-marge.ovh/css/a-la-marge.css');</script>
    <script>import { fr } from 'netlify-cms-locales';CMS.registerLocale('fr', fr);</script>

I think this should be explicit in the documentation if it's a normal behavior.

I finally fixed this by putting registerPreviewStyle and the registerLocale stuff in different <script> blocs, as following:
    <script<EMAIL_ADDRESS>    <script>CMS.registerPreviewStyle('https://my-blog.com/css/my-blog.css');</script>
    <script>import { fr } from 'netlify-cms-locales';CMS.registerLocale('fr', fr);</script>

I think this should be explicit in the documentation if it's a normal behavior.


AFNetworkReachabilityManager strange behavior

Hello!
I used Reachability manager to track connection to specific domain. I call managerForDomain: to setup manager. After some minutes of debugging i found this strange case in switch (AFNetworkReachabilityManager.m);
- (void)startMonitoring {
...
   switch (self.networkReachabilityAssociation) {
        case AFNetworkReachabilityForName:
            break;
        case AFNetworkReachabilityForAddress:
        case AFNetworkReachabilityForAddressPair:
...
}

Maybe it's just a mistake, or - do we really need that break after first case?
Source code of managerForDomain:
+ (instancetype)managerForDomain:(NSString *)domain {
...
    manager.networkReachabilityAssociation = AFNetworkReachabilityForName;

    return manager;
}

Thanks,
Andrew.

:+1 I get not updates to reachability at all when using host name.

Here is what I can gather on the history of this issue so far:

Originally introduced in 3e60343a15bbf02eeabe90d38e0945d38a6acac6 as a result of #1677 and shipped in 2.1.0
As noted in this comment, @mattt wasn't sure of the original intent of that break statement.
99894d4033d9fb8f8904390c860539366c06e7bd was introduced and removed AFNetworkReachabilityAssociation entirely. Shipped in 2.5.2
e92af05 reverted back to the original behavior in 2.5.3

I'm leaving this as a note to myself. Will need to look further into it tomorrow.

I believe this i fixed in https://github.com/AFNetworking/AFNetworking/pull/3117


[FEATURE] Support serving Grafana from subpath

Description
Grafana can be configured to be served from a subpath, this is useful when running behind reverse proxy.
Why is this needed?
So Grafana can run behind a reverse proxy.
Additional Information
See https://grafana.com/tutorials/run-grafana-behind-a-proxy/

Released in 1.5.0 release


SMS Backup cannot access GMail

Configured GMail to enable IMAP.  Downloaded SMS Backup.
Checked on time and time zone.
Opened SMS Backup.
When I click on "connect to GMail" and then select the account, it says "Could not get token from system."  It offers a browser authentication method which is then denied.
Now what?

Browser auth ticket: #767

@AtomicFlamingo was the app installed via F-Droid (or some other 3rd party store)?

No, just plain old downloaded, via Apple store, I think.

Hm ok. Not sure why the authentication failed in your case. I'd need a debug log or similar. In any case the browser authentication has been fixed and will be released as part of 1.5.11.

Please let us know if the 15.11 fix doesn't work for you https://github.com/jberkel/sms-backup-plus#beta

@mrspete can you try disabling Family Link to verify that this is the case?


fix(image):  fallback-src prop not working when image load error in  lazy

seem to be duplicate of #5026

seem to be duplicate of #5026

不一样，这个是  image 组件


[Fix #4932] Accept configuration for Lint/Syntax

Rubocop forbids configuration the Lint/Syntax cop so it doesn't
get disabled. This is failing when loading the default rubocop
configuration from rubocop. This changes it to accept configuration
that doesn't differ from the default.

Before submitting the PR make sure the following are checked:

[ ] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[ ] Used the same coding conventions as the rest of the project.
[ ] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[ ] All tests(rake spec) are passing.
[ ] The new code doesn't generate RuboCop offenses that are checked by rake internal_investigation.
[ ] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[ ] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

@bbatsov I see you reverted this PR. Would you mind giving a bit of context?

Hmm, I don't remember doing this at all. I wonder if I did some mistake or had something in mind...

Actually you did it on a branch - I don't know why I didn't realize that in the first place: https://github.com/bbatsov/rubocop/commits/revert-5153-syntax_config. But I couldn't find any issue / anything else relating to this, that's why I was wondering if anything was wrong.


add 'project' process guidlines for larger contributions

Fixes https://github.com/rust-lang/miri/issues/3443
I am honestly not entirely sure what the consensus from what issue was. I feel like the epoll PR worked reasonably well, and not having been closely involved I am not sure which process @oli-obk followed there. Compared to the first draft in #3443 I tried to make this less formal and framed more as guidelines than hard rules.

The only disagreement I had with you on the issue was whether this guidance would have prevented a past problem.
I'm quite happy with the wording here.

:pushpin: Commit d37e731a40ec6cf0db153cd693bb1d46fff393f1 has been approved by oli-obk
It is now in the queue for this repository.

:hourglass: Testing commit d37e731a40ec6cf0db153cd693bb1d46fff393f1 with merge 95d3adcfbd5f12906c0647687a57a566f7b776d8...

:sunny: Test successful - checks-actions
Approved by: oli-obk
Pushing 95d3adcfbd5f12906c0647687a57a566f7b776d8 to master...


Changed  type hinting from array to ArrayAccess.

Because of the type hinting am not able to pass an ArrayObject as a container.
Passing an array is not possible for me, as i will have to pass it around by reference.
and laravel IOC while resolving wont pass the paraments  by reference.
the solution i found is to make the container an object ie: ArrayObject, as it will be passed by reference.
But the type hinting was preventing me from doing so.

As you can see by the test failures in Travis, your proposed change is a breaking change. By changing it to \ArrayAccess, arrays will no longer work.
I you are having trouble with how the Laravel IoC container works with this object, then I suggest wrapping it with a custom object.
<?php

namespace Your\Project;

use GuzzleHttp\Middleware;

class HistoryMiddleware
{
    private $nextHandler;

    public function __invoke(RequestInterface $request, array $options)
    {

    }
}

@codbox How about https://github.com/guzzle/guzzle/pull/1373 as an alternative. This should meet your needs and still be backward-compatible.

Closing in favor of #1373

Thanks, that works great.


Npm audit

700+ vulnerabilities show up when running 'npm audit'. This fixes most of the easy ones but some others still remain.

Any update on this? @optimization-js @iaroslav-ai
What steps must be taken to fix the remaining ones? @bleakley


Remove Cookie workaround for .NET 7

https://github.com/microsoft/reverse-proxy/pull/451/files#diff-0a4324a1a2cfc979ba03a1cd37836a44d3184f221cf82a121cad58dac3423d3bR419
This has been fixed in Kestrel so the mitigation can be #if removed for .NET 7
https://github.com/dotnet/aspnetcore/pull/41591

Triage: Should be simple once #1727 adds 7.0 target.


Can't build on Rustc > 1.80

Build logs: https://github.com/srd424/nsncd/actions/runs/10235189099/job/28315666470#step:6:83
Upstream issue: https://github.com/rust-lang/rust/issues/127343
This has been fixed on time 0.3.35. We transitively depend on time from time -> slog-term.

Fixed by https://github.com/twosigma/nsncd/pull/123.


Adds paragraph for bdelespierre/underscore.php lib in #links

Hey,
It's been a while since I've been developping, testing and using my own port of Underscore in PHP. This is an updated version of brianhaveri/Underscore.php which includes features that weren't possible at the time Brian made his version (mostly some new PHP stuff like closures contexts and late static binding).
I invite you to discover it here and to let me know if you have any comment or suggestion :+1:

If @brianhaveri agrees, should we just simple change where the Underscore.php link points to?

I think @brianhaveri will not respond to this; I proposed him to step in several weeks ago and got no response. I will modify the PR as @jashkenas stated.

Agreed that the version we currently link to is pretty dead. I've noticed http://anahkiasen.github.io/underscore-php/ as well, which seems more poplar than @bdelespierre's version. However, it looks like it diverges significantly from the API.
I'm not sure exactly what our criteria is for which libraries should be included in this list, or why we even have the list in the first place. I see that it provides some validation of the popularity and influence that Underscore has had on the broader developer community, but I would be surprised if a port of Underscore's API would ever really be successful or even a good idea in another language.
All that philosophizing aside, I'm going to merge this since this version seems more active than the one to which we are currently linking. I'll also tag @anahkiasen to get his input.
I'll followup with another commit to clean up the word-wrapping.


RequestAccount always return null

hello,
i need to get user's phone number through account, but account and error are both null.
is there anything i need to check?
(response type is Accesstoken, and login is completed.)
`public Task GetCurrentAccount(AKFResponseType responseType)
{
var taskCompletionSource = new TaskCompletionSource();
		InitAK(responseType);

		accountKit.RequestAccount((acc, error) =>
		{
			if (error != null)
			{
				taskCompletionSource.SetResult(null);
				return;
			}

			var account = acc as IAKFAccount;
			taskCompletionSource.SetResult(account);
		});

		return taskCompletionSource.Task;
	}`

I just updated the latest version and sample. I got this message [AccountKit][Error]: Invalid OAuth 2.0 Access Token.
Still investigate why it happens.

@donnan924 Plz try again in one hour. I think I found the root cause.


Remove prometheus_ prefix from metrics

This can now be added by users of the library as needed with the new
https://godoc.org/github.com/prometheus/client_golang/prometheus#WrapRegistererWithPrefix
(The latter to be done in the prometheus/prometheus repo separately, going along with a vendoring update.)
@gouthamve @brancz
Signed-off-by: beorn7<EMAIL_ADDRESS>

And also @grobie as he chimed in on the old PR.

lgtm :+1:

As long as the metric names in Prometheus don't change, totally cool with this change.

👍

As long as the metric names in Prometheus don't change, totally cool with this change.

That's the idea.

Follow-up PR for prometheus/prometheus is being worked on.

I believe we should revert this PR, "tsdb_" is a very generic prefix as there are many many tsdb out there.


Add DisableErrSkip option to span status

Adding a DisableErrSkip option to TraceOptions in order to be able to suppress driver.ErrSkip errors in spans.
Right now, it's really annoying to see many "non-real failures" reporting in the tracing dashboard (many spans with status != 0), since ocsql sets the span's status to non zero when the error is driver.ErrSkip, which is not a real failure.
I'm keeping the behavior backward compatible by disabling the error reporting only when this option is being set explicitly.
Attaching here screenshots with before/after:

Before:

After - span with driver.ErrSkip still hold the message, but are not reported as errors:

Awesome package, thanks for creating this.

Totally. This issue was addressed in zipkin instrumentation for go SQL:
https://github.com/jcchavezs/zipkin-instrumentation-sql/pull/3
søn. 23. jun. 2019, 23:35 skrev Ariel Mashraki<EMAIL_ADDRESS>
Adding a DisableErrSkip option to TraceOptions in order to be able to
suppress driver.ErrSkip
https://golang.org/pkg/database/sql/driver/#ErrSkip errors in spans.
Right now, it's really annoying to see many "non-real failures" reporting
in the tracing dashboard (many spans with status != 0), since ocsql sets
the span's status to non zero when the error is driver.ErrSkip
https://golang.org/pkg/database/sql/driver/#ErrSkip, which is not a
real failure.
I'm keeping the behavior backward compatible by disabling the error
reporting only when this option is being set explicitly.
Attaching here screenshots with before/after:

Before:

[image: before1]
https://user-images.githubusercontent.com/7413593/59982208-52dadc80-9617-11e9-8e28-cd6d988a72c6.png
[image: before2]
https://user-images.githubusercontent.com/7413593/59982207-52dadc80-9617-11e9-85b9-e015f869b6ec.png

After - span with driver.ErrSkip still hold the message, but are not
reported as errors:

[image: after 1]
https://user-images.githubusercontent.com/7413593/59982239-b9f89100-9617-11e9-8a7c-b3ea1f0e0bbf.png
Awesome package, thanks for creating this.
You can view, comment on, or merge this pull request online at:
https://github.com/opencensus-integrations/ocsql/pull/37
Commit Summary

Add DisableErrSkip option to span status

File Changes

M driver.go
https://github.com/opencensus-integrations/ocsql/pull/37/files#diff-0
(45)
M options.go
https://github.com/opencensus-integrations/ocsql/pull/37/files#diff-1
(10)

Patch Links:

https://github.com/opencensus-integrations/ocsql/pull/37.patch
https://github.com/opencensus-integrations/ocsql/pull/37.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opencensus-integrations/ocsql/pull/37?email_source=notifications&email_token=AAXOYAWQMIID3JKABASAKC3P37UBNA5CNFSM4H2Z2LB2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3FIBYQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXOYAQ5NO5W7R25BXDCOG3P37UBNANCNFSM4H2Z2LBQ
.


Add --limit-context flag

nix-diff --limit-context will now print at most 3 lines of context around each change. It's limited to 3 lines because that's all I could easily figure out how to implement, given the last time I wrote any Haskell was probably in school lessons about 5 years ago.
Is really only useful in combination with --line-oriented, because otherwise it will print at most 3 words or 3 characters of context, which is... probably unhelpful.
Would fix #42, but I figure you probably don't want to actually merge code this bad :) Also I did not update the tests at all.
Feel free to take the code or not; I probably do not have the motivation to figure out a better implementation of this, though, sorry.

I put up a PR along the same lines of what you're doing here: https://github.com/Gabriella439/nix-diff/pull/81
Let me know if that works for you


ui: add a new API to store and retrieve user-specific metadata such as favorites

Is your feature request related to a problem? Please describe.
zot UI intends to store and retrieve user-specific metadata such as favorites, stars, etc for repos and images.
Describe the solution you'd like
Design and implement an API. This can be under UI extension in the config.

landing page
For favorites, call the new /username/favorites api
For recently updated packages, call the updated /imageListWithLatestTag api, and identify recently updated packages with new flag isRecentlyUpdated

explore page
Add these properties in existing ImageListWithLatestTag
isRecentlyUpdated
isSigned
downloads
Rating (rank)
Stars (count)

Add these properties in existing expanded repo info api ExpandedRepoInfo
At manifest level:
lastUpdated

At layer level:
OS/Arch

For Dependencies
New API to get list of dependencies for all versions

For Dependants
New API to get list of dependants for all versions

TODO: write a document to design "State management in zot"

In testing: https://github.com/project-zot/zot/pull/968/commits/0470527795de7a97c7fe765492af62a28cdbdc48


fix on going errors in transformers unit tests

This PR anchors the version of transformers in the requirements file to ensure that all unit tests succeed. They have been failing with the more recent versions of the transformers package via AttributeError: 'Trainer' object has no attribute '_pad_across_processes'

/ok to test

/ok to test

/ok to test

/ok to test

closing because handled in https://github.com/NVIDIA-Merlin/Transformers4Rec/pull/757


Update<EMAIL_ADDRESS>class name

Signed-off-by: Paul S. Schweigert<EMAIL_ADDRESS>Fixes func v0.22 class name, as reported on slack

we are paying technical debt by not having a script that does this bump
/lgtm

/approve

/assign @gab-satchi

/lgtm
/approve


[FeatureRequest] Kubernetes - add API Master meta label for multi cluster setups

Hi all,
In a multi cluster setup, it currently looks impossible (unless you use hard coded external_label with cluster specific meta-data) to determine the source cluster from which the metrics are originated. Would it be possible to add a label to add this kind of information?
# kubectl cluster-info
Kubernetes master is running at https://vm-48-124.eng.lab.tlv.redhat.com:8443

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

Having an extra label that adds the Kubernetes Master URL would be sufficient to distinguish logs in a multi cluster environment.
Best regards,
Bart

Are you looking to add a label to everything that comes from a given scrape_config? If so, relabelling already allows for this.

Hi @bruan-brazil , labeling / relabeling / external label ... All the same for me. I want to be able to fetch the information (like the pod name is added automatically) without having to hard code this values in the Prometheus config file.

Does a kubernetes cluster have a notion of its own name? Or is it something that's just operational practice on your side?
Given that you have to have a scrape config per cluster anyway, relabelling is the way to go here I suspect.

@boeboe can you describe further what you are doing? Are you looking at multiple clusters with the same Grafana instance and are trying to distinguish? Are you trying to use Prometheus Federation and fan in from multiple Prometheus instances?

Does a kubernetes cluster have a notion of its own name?

As far as I'm aware it does not, the only reason you are getting a URL there @boeboe is because kubectl is printing the DNS name it itself is using to access the clusters apiserver, which in turn likely gets us to @brian-brazil's conclusion (if we have the full picture):

Given that you have to have a scrape config per cluster anyway, relabelling is the way to go here I suspect.

Hi @brancz and @brian-brazil ,
Thanks for your responses so far!
We have a HA cluster setup with 2 clusters in different private data centers. Within the K8S cluster itself, we use one Prometheus instance, which acts as a mere proxy to another Prometheus instance outside of the cluster (due to permanent storage reasons). The Grafana visualisations origin from this second out-of-k8s-cluster instance.
What I am trying to achieve is to have a single deployment yaml file for the Prometheus proxy deployments in both clusters. If there is a way to dynamically enrich the metrics (from the node-exporters deployed as a K8S daemon set) with the cluster Master URL (the only thing that makes metrics unique cross-cluster). What I do now is to use an external_labels named cluster to add this extra information statically (resulting in separate yaml deployment files cross cluster).
We had a similar "issue" with regards to EFK (ElasticSearch, Fluentd and Kibana), but I have found a solution and created a pull request for this on the following Github Repo's:

https://github.com/abonas/kubeclient/issues/245
https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/pull/70

I tried to find a way to do something similar here, but so far failed to find an elegant solution...
Best regards,
Bart

What I do now is to use an external_labels named cluster in the global configuration section of the Prometheus proxy to add this extra information statically

That's the recommended way of handling that. I'ts expected that each Prometheus server you're running will have different external_labels.

Hi @brian-brazil
Ok I see your point. I was wondering if there is any way to execute arbitrary shell commands or execute some interpreted language within the configuration files of Prometheus?
An example... in fluentd configuration files, one is able to do the following:
<filter **>
  @type record_transformer
  <record>
	cluster "#{%x[ grep search /etc/resolv.conf | awk '{print $NF}' ]}"
  </record>
</filter>

This is a way to dynamically add cluster information (I'm no big fan of hard coded configuration when not needed, as you might suspect) being the cluster API server DNS search name, which is a temporary work around before the feature as implemented in the pull request is released as an official Ruby Gem. So my question now to end up, is whether there is a way to have things executed/interpreted at run/start-up time in the Prometheus configuration file?

Ok I see your point. I was wondering if there is any way to execute arbitrary shell commands or execute some interpreted language within the configuration files of Prometheus?

No, and that's explicitly out of scope. That's the role of your configuration management system.

Ok,
Actually a very good point there. Thanks for the feedback and patience.
BR,
Bart


Build error in Xcode 16 / iOS18

Describe the bug
Ref https://github.com/DataDog/dd-sdk-ios/issues/1892
ios/Pods/DatadogCore/DatadogCore/Sources/Core/Upload/BackgroundTaskCoordinator.swift:29:26 Type 'UIApplication' does not conform to protocol 'UIKitAppBackgroundTaskCoordinator'

Reproduction steps
Try build in Xcode16/iOS18
SDK logs
No response
Expected behavior
Upgrade new dd-sdk-ios
Affected SDK versions
2.5.0
Latest working SDK version
No response
Did you confirm if the latest SDK version fixes the bug?
Yes
Flutter Version
No response
Setup Type
No response
Device Information
No response
Other relevant information
No response

Hi @ChanghyeonYoon ,
As you mentioned, this was reported in the iOS SDK as part of https://github.com/DataDog/dd-sdk-ios/issues/1892 and was fixed in their latest release.
I'm planning a Flutter release some time next week to include updated native SDKs.

Hi @ChanghyeonYoon ,
As you mentioned, this was reported in the iOS SDK as part of DataDog/dd-sdk-ios#1892 and was fixed in their latest release.
I'm planning a Flutter release some time next week to include updated native SDKs.

Can I try new release version now?
Because I can't build now...... :(

pod 'DatadogCore', '2.13'
pod 'DatadogLogs', '2.13'
pod 'DatadogRUM', '2.13'
pod 'DatadogInternal', '2.13'
pod 'DatadogCrashReporting', '2.13'

[!] CocoaPods could not find compatible versions for pod "DatadogRUM":
  In snapshot (Podfile.lock):
    DatadogRUM (= 2.11.0)

  In Podfile:
    DatadogRUM (= 2.13)

    datadog_flutter_plugin (from `.symlinks/plugins/datadog_flutter_plugin/ios`) was resolved to 0.0.1, which depends on
      DatadogRUM (= 2.11.0)

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * changed the constraints of dependency `DatadogRUM` inside your development pod `datadog_flutter_plugin`.
   You should run `pod update DatadogRUM` to apply changes you've made.

I can't override pod follow this error... :(

It will be same error even try update

The Datadog Fluttter SDK 2.6.0 is out now and should fix this.


Replace symlink resolution with realpath

Credit: @jasonmalinowski
Fixes https://github.com/dotnet/vscode-csharp/issues/6218

Tested on Ubuntu 22.04
No Uri problem


Password error translation not updated on Language change

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to Login page
Don't enter anything and press enter
You'll see an error Please enter an email or phone number
Now change the language to Spanish
You'll see the whole page is translated except for the error message.

Expected Result:
The error message should've been updated with the correct translation text
Actual Result:
Error message translation not updated on language change.

Workaround:
The user will have to click the button again to get the correct error message.
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @greg-schroeder (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Proposal
In the LoginForm.validateAndSubmitForm, we're storing the whole translated error message in the state.
if (!this.state.login.trim()) {
    this.setState({formError: this.props.translate('loginForm.pleaseEnterEmailOrPhoneNumber')});
    return;
}

Instead we should only store the key and use translation in the render method
//validateAndSubmitForm ()
if (!this.state.login.trim()) {
    this.setState({formError: 'loginForm.pleaseEnterEmailOrPhoneNumber'});
    return;
}

// render()

{this.state.formError && (
    <Text style={[styles.formError]}>
        {this.props.translate(this.state.formError)}
    </Text>
)}

The same issue exists in PasswordForm too.

Also the error message is a little misleading when there's only one field it says, Please fill out all fields

Triggered auto assignment to @timszot (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Triggered auto assignment to @dylanexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Working on this now

Posted job

Internal: https://www.upwork.com/ab/applicants/1427574146811060224/job-details
External: https://www.upwork.com/jobs/~013c836a62663e632e

Triggered auto assignment to @puneetlath (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@puneetlath, @dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

Triggered auto assignment to @Jag96 (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

re-labeled as Puneet is deep in allocations!

I propose that I think we are better off following the same implementation as on the login forms.
Where we would add the same response handling logic found here:
https://github.com/Expensify/App/blob/8a5cf2d190e8e259a1bcb4090fcb437e42f78dbe/src/libs/API.js#L222-L251
to resetPassword and changePassword
and then use:
translateLocal(error.message)
like:
https://github.com/Expensify/App/blob/8a5cf2d190e8e259a1bcb4090fcb437e42f78dbe/src/libs/actions/Session.js#L229-L231
to set the error which will be consumed by:
https://github.com/Expensify/App/blob/8a5cf2d190e8e259a1bcb4090fcb437e42f78dbe/src/pages/SetPasswordPage.js#L106
and
https://github.com/Expensify/App/blob/8a5cf2d190e8e259a1bcb4090fcb437e42f78dbe/src/pages/settings/PasswordPage.js#L169
I think we should also move this error handling for the login API error codes out of the API.js and into the actions files to keep the API file size down.

@anthony-hull the error that I reported was more of UI issue even before hitting any API. If you notice the error has translation but it doesn't switch translation on language change.
Your solution might be an extension/separate enhancement for API error handling. I am not sure if any issues exist with that. You can create an issue with relevant data/screenshots etc.

Ahh. Yes I see good point!

Fix has been on production for 7 days without regression, paid + bonus!


[Improvement]: AMS frequently print warning logs of 'Unclosed ResolvingFileIO'

Why are the changes needed?

Close #2024 .
Brief change log

Tested OK in local env.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 27.18%. Comparing base (9def89f) to head (b9024d9).
Report is 3 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #3124      +/-   ##
============================================
- Coverage     27.64%   27.18%   -0.46%
+ Complexity     2496     2462      -34
============================================
  Files           360      363       +3
  Lines         37133    37471     +338
  Branches       5372     5400      +28
============================================
- Hits          10265    10187      -78
- Misses        25908    26327     +419
+ Partials        960      957       -3

Flag
Coverage Δ

trino
27.18% <ø> (-0.46%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@tcodehuber Some conflicts may need to be fixed.

@tcodehuber Some conflicts may need to be fixed.

Fixed. @zhoujinsong

Thanks for the contribution! @tcodehuber


rules: Use Camel format

Use Camel format.
Signed-off-by: johncming<EMAIL_ADDRESS>

I don't think using camel cases for package names is the convention. https://blog.golang.org/package-names and some other blog posts tell me that using _ is also not a good practice in Go. html_template should be just htmltemplate, and similarly many other renames in this codebase (for example tsdb_errors).

I don't think using camel cases for package names is the convention. https://blog.golang.org/package-names and some other blog posts tell me that using _ is also not a good practice in Go. html_template should be just htmltemplate, and similarly many other renames in this codebase (for example tsdb_errors).

Yes, you're right, both camel and underline are not recommended in go.


extract-18n skip some modules

Describe the bug
I have an angular app developped with lazy-loaded modules architecture. I have a CoreModule, a SharedModule and some features modules grouped in the features folder. When I run ng extract-i18n it extract every string marked for translation inside the features folder but none of those inside CoreModule and SharedModule.
Setup/Configuration
The extract-i18n entry in my angular.json file is like below :
"extract-i18n": {
          "builder": "ng-extract-i18n-merge:ng-extract-i18n-merge",
          "options": {
            "browserTarget": "melofeel-front:build",
            "format": "xlf2",
            "outputPath": "src/locale",
            "targetFiles": [
              "messages.fr.xlf"
            ],
            "sort": "idAsc"
          }
        },

Expected behavior
I'd like to have all the marked string to appear in my messages.fr.xlf file.
Version (please complete the following information):

Angular: 14.2.12
OS: Win10
nodejs: 18.12.1
ng-extract-i18n-merge version: 2.5.1.

Hi @JleHi
Thanks for reporting this!
Would you be able to share a (minimal) reproduction? Preferably a git repo I could checkout and run npm install with a subsequent ng extract-i18n on to reproduce it.

Hi @daniel-sc ,
Thanks for your answer.
I've created a git repo on Github as you asked. I hope it is accessible, it's my first one : https://github.com/JleHi/repro-extract-i18n-missing-translations/
I can't post the project as it is so I made a short version of it for your tests. It has a slightly different comportment than the other: this one take the translations from CoreModule in account. But like the other the SharedModule seems to be ignored.
I've done this one in a hurry before leaving, let me know if something is wrong.
Thanks again.

@JleHi thanks for providing a reproduction!
It seems that the component in your shared module was not at all used in your application - this directly implies that the translations from this component cannot be extracted by angular (and cannot be managed by this plugin).
To prove this, I used the shared component in one of your feature components and then the i18n text is contained in the messages.(fr.)xlf - see https://github.com/JleHi/repro-extract-i18n-missing-translations/pull/1
Please reopen, if there is some other problem I overlooked!


Log info messages to stdout instead of stderr

so that actual errors are more visible

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add KernelMemoryService

Add Cosmos DB - whichever flavor works best with SK memory (SQL?) to /infra bicep. Take note regional requirements. Note down important choices in readme.

Renaming from Add Cosmos DB to Add KernelMemoryService since I want to use KernelMemoryService to handle both memory and knowledge management...

Changing back as KernelMemory is too recent - not enough documentation for me to try to hack with at the moment. One day I'll revisit. Hopefully this year.
Add Cosmos DB - whichever flavor works best with SK memory


version of wiki data and how to update database?

I want to know what version of wiki data used for database and keep it up to date. Can you guide me?

I'd also would be interested in that how to, with the additional question:
What would I have to do to make the entity linker work with the German or French version of Wikipedia/wikidata?
Cheers
Werner

I would also be interested in how the data is processed. Trying to interpret how the SQLite database is structured.. It looks like you are using some special IDs (279,31) to designate certain aliases as "instances".  It would be great to get a script that processes raw wikidata dumps!
Thanks for sharing, this is great.


Amplify Publish Fails with uninformative error

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.15.0
Amplify CLI Version
10.8.1
What operating system are you using?
wsl2 on Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
All changes were made through the CLI.
Describe the bug
When I perform publish for the first time on my amplify application it completes the entire publishing process and even says it does so successfully, but it doesn't do it successfully.
The error that appears is: ⠇ Deploying build artifacts to the Amplify Console..Job failed.{"jobArn":"arn:aws:amplify:ap-southeast-2:121647937745:apps/d382eiebk7ozg/branches/dev/jobs/0000000005","jobId":"5","commitId":null,"commitMessage":"Deployment failed","commitTime":null,"startTime":"2023-03-23T11:16:53.429Z","status":"FAILED","endTime":null,"jobType":null}
Expected behavior
My amplify application is published
Reproduction steps

Run amplify publish locally.

Project Identifier
Project Identifier: b49b46a13c132ba3c24b58950f212eda
Log output

# Put your logs below this line
2023-03-23T10:32:15.684Z|info : amplify publish core
2023-03-23T10:32:15.739Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:32:18.192Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:32:18.193Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:32:18.193Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:32:18.202Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:32:18.202Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:32:18.203Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:32:18.209Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2023-03-23T10:32:18.209Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T10:32:19.176Z|info : amplify-provider-awscloudformation.initialize-env.run.cfn.updateamplifyMetaFileWithStackOutputs([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:32:19.178Z|info : amplify-provider-awscloudformation.aws-cfn.updateamplifyMetaFileWithStackOutputs.cfn.listStackResources([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:32:19.704Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:32:20.237Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]ch99f4eb0f-[***]199RYB/[***]e920-[***]0b-[***]ed-[***]b2-[***]393ea"}])
2023-03-23T10:32:20.239Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]fyhosting-[***]ROMEE/[***]d170-[***]0b-[***]ed-[***]40-[***]3d720"}])
2023-03-23T10:32:21.510Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]ify-[***]json","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T10:33:01.661Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:33:01.663Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:33:01.663Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:44:10.875Z|info : amplify configure core project
2023-03-23T10:44:10.934Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:47:09.191Z|info : amplify configure core project
2023-03-23T10:47:09.252Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:47:32.897Z|info : amplify configure core project
2023-03-23T10:47:32.955Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:49:08.297Z|info : amplify configure core project
2023-03-23T10:49:08.354Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:53:25.455Z|info : amplify push core
2023-03-23T10:53:25.514Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:53:26.722Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:53:26.723Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:53:26.723Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:53:26.743Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:53:26.744Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:53:26.744Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:53:26.749Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2023-03-23T10:53:26.750Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T10:53:27.252Z|info : amplify-provider-awscloudformation.initialize-env.run.cfn.updateamplifyMetaFileWithStackOutputs([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:53:27.253Z|info : amplify-provider-awscloudformation.aws-cfn.updateamplifyMetaFileWithStackOutputs.cfn.listStackResources([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:53:27.596Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:53:27.944Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]ch99f4eb0f-[***]199RYB/[***]e920-[***]0b-[***]ed-[***]b2-[***]393ea"}])
2023-03-23T10:53:27.947Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]fyhosting-[***]ROMEE/[***]d170-[***]0b-[***]ed-[***]40-[***]3d720"}])
2023-03-23T10:53:28.204Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]ify-[***]json","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T10:53:28.637Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:53:28.638Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:53:28.638Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:53:34.991Z|info : amplify publish core
2023-03-23T10:53:35.050Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:53:36.122Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:53:36.123Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:53:36.123Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:53:36.132Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:53:36.132Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:53:36.132Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:53:36.141Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2023-03-23T10:53:36.142Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T10:53:36.466Z|info : amplify-provider-awscloudformation.initialize-env.run.cfn.updateamplifyMetaFileWithStackOutputs([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:53:36.467Z|info : amplify-provider-awscloudformation.aws-cfn.updateamplifyMetaFileWithStackOutputs.cfn.listStackResources([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:53:36.737Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:53:37.123Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]ch99f4eb0f-[***]199RYB/[***]e920-[***]0b-[***]ed-[***]b2-[***]393ea"}])
2023-03-23T10:53:37.126Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]fyhosting-[***]ROMEE/[***]d170-[***]0b-[***]ed-[***]40-[***]3d720"}])
2023-03-23T10:53:37.378Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]ify-[***]json","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T10:54:17.183Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:54:17.189Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:54:17.190Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:56:58.592Z|info : amplify publish core
2023-03-23T10:56:58.654Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T10:57:00.220Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:57:00.221Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:57:00.221Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:57:00.230Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["EDhance Amplify"])
2023-03-23T10:57:00.230Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"ap-southeast-2"}])
2023-03-23T10:57:00.230Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["EDhance Amplify"])
2023-03-23T10:57:00.235Z|info : amplify-provider-awscloudformation.zip-util.downloadZip.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip"},null])
2023-03-23T10:57:00.241Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]rent-[***]ud-[***]d.zip","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T10:57:00.591Z|info : amplify-provider-awscloudformation.initialize-env.run.cfn.updateamplifyMetaFileWithStackOutputs([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:57:00.593Z|info : amplify-provider-awscloudformation.aws-cfn.updateamplifyMetaFileWithStackOutputs.cfn.listStackResources([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:57:00.944Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]ify-[***]peach-[***]ev-[***]430"}])
2023-03-23T10:57:01.335Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]ch99f4eb0f-[***]199RYB/[***]e920-[***]0b-[***]ed-[***]b2-[***]393ea"}])
2023-03-23T10:57:01.338Z|info : amplify-provider-awscloudformation.aws-cfn.describeStack.cfn.describeStacks([{"StackName":"[***]rmation:ap-[***]east-[***]45:stack/[***]ify-[***]peach-[***]ev-[***]430-[***]fyhosting-[***]ROMEE/[***]d170-[***]0b-[***]ed-[***]40-[***]3d720"}])
2023-03-23T10:57:01.636Z|info : amplify-provider-awscloudformation.aws-s3.s3.getFile([{"Key":"[***]ify-[***]json","Bucket":"[***]ify-[***]peach-[***]ev-[***]430-[***]ment"}])
2023-03-23T11:01:03.869Z|info : amplify publish core
2023-03-23T11:01:03.929Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}
2023-03-23T11:02:00.450Z|info : amplify version core
2023-03-23T11:02:40.854Z|info : amplify diagnose core  {"send-report":true,"yes":false}
2023-03-23T11:02:40.912Z|info : amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

hey @adamparslow, thank you for reaching out. From the App ID in the output on diving into the console build logs we observed that the publish failed as the artifact being upload to the console build is an SSR application.
Does the application utilizes any SSR frameworks such as Next.js? if yes, currently Amplify console does not support manual deploys for SSR.
But the error message can be modified to provide a better reason for failure. I will be marking this as a bug for error enhancements.

Ah thank you for that. Yes I am using Next.js SSR, that must be the problem. I appreciate your help!


fix(l10n): New translations

:tada: This PR is included in version 2.18.12 :tada:
The release is available on:

GitHub release
v2.18.12

Your semantic-release bot :package::rocket:


Postals sent by the call911 command are incorrect

What version of Node.js are you using?
18.4.1
What version of npm are you using?
9.3.1
What operating system are you using?
Ubuntu 22.04.2 LTS
What version of SnailyCAD are you currently using?
1.48.2
Describe the Bug
911 calls (/call911) report the correct road, but incorrect postal number. This is using sna-postals with the postals that ship with sna-postals(unmodified). sna-postals is installed per the documentation, and the CAD is fully integrated with working live map.
You can see from the attached screenshot, the player coords and postal file with the current location highlighted. However, as depicted in the screenshot, the postal that is reported in CAD is incorrect. Our CAD has no custom addresses, so that has been eliminated as a source of the issue.

Expected Behavior
My expectation of what should occur with a /call911 command is that the 911 call that gets added to the CAD have the players current postal instead of one across the map from the player.
To Reproduce
To reproduce, install the CAD and sna-postals per the documentation. Install fiveM integrations per CAD documentation. In FiveM game chat, type the command /call911 and add a message. The 911 call will be sent to the CAD, but the postal information will be incorrect.
No custom addresses are required to be populated into the CAD.

This has been fixed in the latest version of the fivem-integrations. You will have to update all installed integrations for this to properly work.


Getting compile error.

fatal error: HID.h: No such file or directory
#include "HID.h"
compilation terminated.
exit status 1
Error compiling for board Digispark (Default - 16.5mhz).
helppp

Thanks for trying to use my project.  Moreover, I have a lot of other work now and I don't really want to return to the project. I have not encountered such a problem as yours, so I cannot offer a solution. Try installing software and libraries from two years ago, there may be an update issue. In this case, Google is a better assistant than me.
Good luck.

i have solved the problem (uploaded the wrong sketch LOL)
have a great day.
thanks a lot
On Mon, Sep 20, 2021 at 11:03 AM Kovynev Maxim @.***>
wrote:

Thanks for trying to use my project.  Moreover, I
have a lot of other work now and I don't really want to return to the
project. I have not encountered such a problem as yours, so I cannot offer
a solution. Try installing software and libraries from two years ago, there
may be an update issue. In this case, Google is a better assistant than me.
Good luck.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kovinevmv/DigiSparkStealer/issues/8#issuecomment-922708816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVWU3H37537CLFLZ4O7H6LLUC3TFHANCNFSM5ELL6Z6Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Sacrificial lamb joker

sacrificial_lamb.lua in the joker folder and edited paperback.lua to enable it

I mostly just used the context and description from campfire as its effect is pretty close to this one, but i'll try to find a context that applies to destroyed cards

Is this ever getting fixed? lol

@BBBalatroMod I can work on this and get it finished if you are busy and can't work on it


Improve performance of DictionaryArray::try_new()

Which issue does this PR close?
Closes #1313.
What changes are included in this PR?
extract the dictionary validation logic out of ArrayData::validate_full into a separate function.
DictionaryArray::try_new  use the ArrayDataBuilder::build_unchecked and afterwards call the new function which only validates that the keys are in bounds.
Are there any user-facing changes?
None

Codecov Report

Merging #1435 (b9b79cf) into master (d9099c4) will decrease coverage by 0.00%.
The diff coverage is 89.28%.

@@            Coverage Diff             @@
##           master    #1435      +/-   ##
==========================================
- Coverage   82.68%   82.67%   -0.01%
==========================================
  Files         185      185
  Lines       53822    53825       +3
==========================================
- Hits        44502    44501       -1
- Misses       9320     9324       +4

Impacted Files
Coverage Δ

arrow/src/array/data.rs
82.82% <88.00%> (-0.34%)
:arrow_down:

arrow/src/array/array_dictionary.rs
91.73% <100.00%> (+0.07%)
:arrow_up:

arrow/src/datatypes/field.rs
53.79% <0.00%> (-0.31%)
:arrow_down:

arrow/src/array/transform/mod.rs
86.31% <0.00%> (-0.12%)
:arrow_down:

arrow/src/array/array_list.rs
95.52% <0.00%> (ø)

parquet/src/encodings/encoding.rs
93.71% <0.00%> (+0.19%)
:arrow_up:

parquet_derive/src/parquet_field.rs
66.43% <0.00%> (+0.22%)
:arrow_up:

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 d9099c4...b9b79cf. Read the comment docs.

I have read the conversion above. thanks @viirya @alamb .
I add the cheap validate() and a unit test for wrong dictionary key.

Looks good -- thank you @jackwener  and @viirya

lgtm


Support proto files in subdirectories of the package directory

The existing code assumed that all input .proto files were in the same directory as the BUILD file for the build rule. This isn't always the case, since it's perfectly legal to reference files in a subdirectory that doesn't have its own BUILD file.

Based on top of #434 to make tests work locally, and in the hope it will be merged soon.


Dia umpire goes conda

[ ] tests missing

ping @jj-umn

@jj-umn can you please add tests to this tool. I have no clues about it, sorry.


k3s: package k3s-killall.sh script

Describe the bug
k3s provides a a k3s-killall.sh script that is required for orderly shutdown. (remove iptables rules, stop running containers, ...). Also k3s-uninstall.sh which cleans up all related directories.
Those is currently not included in the k3s package.
While not very complicated scripts, it would be nice to have them. (And track upstream changes)
Notify maintainers
@euank

Note that the scripts are created inside install.sh: https://github.com/rancher/k3s/blob/7ca50efb8b6c5218690e3f1a0a8df4b9843bb3e1/install.sh#L351

I agree those are handy scripts to have around.
I think we may end up just wanting to fork em since the systemd related stuff won't work on nixos I think.
In a normal k3s installation, the systemd unit files are dropped in etc by install.sh and can be deleted / stopped reasonably.
On nixos, those systemd unit files are created / started / managed by the nixos module and nixos-rebuild, so having those scripts stop/remove them doesn't seem right.
For the other state nixos doesn't manage (the stuff in /var/lib*, running containers, etc), having those makes sense.

There's a few additional choices here which add complexity.
It's sometimes desirable for resources to keep running when k3s is stopped, most notably it's usually desirable for kubernetes pods and networking to keep working during a k3s upgrade, during which the service is stopped and started.
The killall script expresses the intent that it's desired for all that stuff to go away, but systemctl stop k3s doesn't by itself.

Still an issue, we just haven't gotten to it yet. Un-stale, stalebot

A partial workaround is to change k3s' service configuration to use KillMode=mixed as suggested here: https://github.com/k3s-io/k3s/issues/2400#issuecomment-711065914
systemd.services.k3s.serviceConfig.KillMode = mkForce "mixed";

Running k3s-killall.sh is still required + even after running it I still find a ton of active containerd units:
systemctl list-units|grep -i containerd
  cri-containerd-a65c2668f36e2a1eaf27f86440d3fcbede3c408ce7148b735f0818d670c3e6ff.scope
loaded active running   libcontainer container a65c2668f36e2a1eaf27f86440d3fcbede3c408ce7148b735f0818d670c3e6ff
cri-containerd-a6e5c4e8e0bce2088b59d26967031733b029e82fa6a168ed55e4add8a72c3555.scope
...

These remaining using can be easily because the processes have been properly killed by systemd, e.g. with systemctl list-units|grep -i cri-containerd-|awk '{print $1}'|grep -v ●|xargs -r -P 10 -I {} bash -c "echo systemctl stop {}; systemctl stop {};"

Isn't there a way to hook it automatically to shutdowns? Like adding it to WantedBy=shutdown.target?

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/traefik-oci-container-on-port-80/41882/2