fix: update origin path handling to disallow /

Fixing origin.path handling to not allow "/".

:tada: This PR is included in version 3.2.1-stage.1 :tada:
The release is available on:

npm package (@stage dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: cat redirection

Summary
Closes #109, provided that #195 is also merged in.

Add support for redirection with "<" for cat command only with input file and output file
Error handling to check if file already exists and is a directory (you cannot write to the directory like a file)
Handles the other two cases: file already exists -> overwrite file with output or create the file in the event it does not exist yet
Wipe the output from the cat command (it should not be outputted to stdout)

Test Plan
https://user-images.githubusercontent.com/13056466/211022968-b583c777-b8a5-4151-a310-f6a38f15bd4e.mov

I have a question regarding #109, do we need to add support for pipes? Because there isn't really an example to test with. We could do it with echo, but these examples have to be hardcoded for now unless big refactor. If pipes not needed, then I think this PR completes this project :)

@jason2020 I think we will be alright without pipes for now. Thanks for all of the features. I think you are good so we'll try to wrap up the rest on our end. Thanks! If we decide we need pipes, I'll tackle them myself or we'll let you know. Thanks.


Remove obsolete SetAccess calls

This removes the obsolete SetAccess calls that were removed in Catalina,
and, subsequently, in go-keychain.
There should be no impact to functionality here - I'm assuming that
we'd be using access defaults here now, given that the calls here seem
to have been removed without any alternative.

Hmm, based on https://github.com/99designs/keyring/issues/66#issuecomment-711492701, I'm kind of wondering what we do here. Sounds like this is necessary to ensure there's a password prompt on dependencies that may not affect us per se, but we probably account for anyway. There is a documented API there (use of https://developer.apple.com/documentation/security/1392184-secaclupdateauthorizations) instead, so that sounds like it would be a good jumping point here to try and address this.
Going to stop short on this now for time, but we should probably revisit sooner rather than later so that we can get these warnings out of Boundary development (it does seem like it's breaking a few vim-go commands, guessing maybe because of the warning output it generates).

Going to close this for now to clean up old PRs in my backlog. I think we'll have to defer this until we resolve the issue of actually transitioning the aforementioned API over, versus flat out removing things altogether.


Update .bazelrc

Make sure that no regressions are introduced to build with incompatible_disallow_empty_glob

I will close the PR, anyway this repository seems that is no longer maintained


Contributing.md file

as its an open source so to setup the project we need an contribution file where we have our all the guidelines

this is issue duplicate with #95


probe' overrides a member function but is not marked 'override'

probe' overrides a member function but is not marked 'override'
'start' overrides a member function but is not marked 'override'
'stop' overrides a member function but is not marked 'override'
'setPowerState' overrides a member function but is not marked 'override'

Fixed in master.


.button-link and :active css question

buttons.css has
  &:active:not(:disabled, .disabled),
  &.active:not(:disabled, .disabled) {
    background-color: color(var(--button-bg-color) shade(10%));
    border-color: color(var(--button-bg-color) shade(10%));
    border-top-color: color(var(--button-bg-color) shade(20%));
    border-bottom-color: color(var(--button-bg-color) shade(10%));
  }

However when I click on a .button-link element such as on https://shoelace.style/docs/buttons.html# the :active styling isn't applied. If I apply :active using Chrome Dev Tools it is applied.
IMO for .button-link elements you don't want the :active styling applied, which it isn't.
However I'm curious why it isn't being applied and wonder if this is a  bug of some sort or simply my lack of CSS knowledge.

I guess it's just visual preference. I believe the behavior is consistent with Bootstrap 4. Button links aren't really buttons — they're just links formatted with the same size and spacing so you can use them alongside buttons and maintain a visual consistency.
BTW — that is code from the last beta. It was changed in a recent commit to reduce the selector's specificity. I'll push a new beta sometime next week with all the changes.


Running with dbt=0.18.1 Encountered an error: The library Security could not be found

Describe the bug
Recently upgraded to Mac OS Big Sur and dbt now returns an error when calling dbt deps and other commands
Steps To Reproduce
On Big Sur, run dbt deps
Expected behavior
Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.

System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[ ] bigquery
[x ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.18.1
   latest version: 0.18.1

Up to date!

Plugins:
  - bigquery: 0.18.1
  - snowflake: 0.18.1
  - redshift: 0.18.1
  - postgres: 0.18.1```

**The operating system you're using:**
Mac OS Big Sur
**The output of `python --version`:**
Python 3.7.1
### Additional context
Did some googling and it may be an issue with snowflake and Big Sur compatibility.

Hey @jtalmi, thanks for flagging this. I'm on Big Sur now and I haven't had any issues running dbt deps.

How did you install dbt? What do you see when you run which dbt?
Could you try to identify the version of the snowflake-connector-python library that you have installed for use with dbt?

Ah you are? Ok I saw some stuff related to Big Sur on stack overflow and I just upgraded so I made the assumption.
I installed dbt using pip:
$ which dbt
/Users/jonathantalmi/.pyenv/shims/dbt

$ pip list  | grep snowflake-connector-python
snowflake-connector-python 2.2.10

Hmm ok, I just did a fresh pip install dbt in a virtualenv, using the same version of snowflake-connector-python (I think we pin it tightly), and I was able to run dbt deps. So there must be something else afoot...

If this helps, even after migrating to Big Sur I was able to run dbt 0.18.0 in a previous virtualenv I had installed, managed by pipenv. The pipfile is here:
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]
fire = "==0.2.1"
pandas = "*"
mock = "*"
permifrost = "*"
snapshottest = "==0.5.1"

[packages]
dbt = "==0.18.0"
python-dateutil = "==2.8.0"

[requires]
python_version = "3.7"

I tried to make changes to this pipfile but kept running into a cryptography dependency issue. Event now, when I try to generate a virtualenv using pipenv based on the following, it fails:
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[packages]
dbt = "==0.18.1"

ERROR: Could not find a version that matches cryptography<3,>=2,>=3.2 (from -r /var/folders/w2/12yfgt212f7c6g_tzm_kp4vr0000gn/T/pipenvsc46ijcbrequirements/pipenv-mzhb5zvc-constraints.txt (line 2))
Tried: 0.1, 0.2, 0.2.1, 0.2.2, 0.3, 0.4, 0.5, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.6, 0.6.1, 0.7, 0.7.1, 0.7.2, 0.8, 0.8.1, 0.8.2, 0.9, 0.9.1, 0.9.2, 0.9.3, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.1, 1.1.2, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.4, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.6, 1.7, 1.7.1, 1.7.2, 1.8, 1.8.1, 1.8.2, 1.9, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2, 2.2, 2.2.1, 2.2.1, 2.2.2, 2.2.2, 2.3, 2.3, 2.3.1, 2.3.1, 2.4, 2.4, 2.4.1, 2.4.1, 2.4.2, 2.4.2, 2.5, 2.5, 2.6, 2.6.1, 2.6.1, 2.7, 2.7, 2.8, 2.8, 2.9, 2.9, 2.9.1, 2.9.1, 2.9.2, 2.9.2, 3.0, 3.0, 3.1, 3.1, 3.1.1, 3.1.1, 3.2, 3.2, 3.2.1, 3.2.1
There are incompatible versions in the resolved dependencies:
  cryptography>=3.2 (from -r /var/folders/w2/12yfgt212f7c6g_tzm_kp4vr0000gn/T/pipenvsc46ijcbrequirements/pipenv-mzhb5zvc-constraints.txt (line 2))
  cryptography<3,>=2 (from dbt-snowflake==0.18.1->dbt==0.18.1->-r /var/folders/w2/12yfgt212f7c6g_tzm_kp4vr0000gn/T/pipenvsc46ijcbrequirements/pipenv-mzhb5zvc-constraints.txt (line 3))

See thread here: https://getdbt.slack.com/archives/C2JRRQDTL/p1607011130107300

Hmm. We are definitely upgrading cryptography in dbt v0.19.0, but I don't think we can do it sooner because of the upper bound in the pinned version of snowflake-connector-python here.
What version of pip are you using? For the time being, I wonder if you can use the legacy dependency resolver (--use-deprecated=legacy-resolver). For reference: https://blog.python.org/2020/11/pip-20-3-release-new-resolver.html

Retried using pip==20.2.1 (with the old dependency resolver) and still getting the same cryptography issue as above. As to my original issue...still no idea. Hopefully something pops up on stack overflow soon.

@jtcohen6 the stackoverflow gods smiled on me today. someone solved this by upgrading their version of oscrypto to 1.2.1:
https://stackoverflow.com/questions/65012259/snowsql-fails-with-the-library-security-could-not-be-found-after-upgrading-to
so i ran pip install oscrypto==1.2.1 and it works fine now.


linear model of feature importance

@gwaybio linear modeling PR draft

@gwaybio ready for review!

@gwaybio ready for re-review. I can make any other changes too.
I Addressed main comments:

Please output only one file for coefficients (rather than splitting out into separate files). One file is way easier to wrangle later. You may have to add some identifier columns.
Addressed
Please also output PNGs for the figures, which are quicker to see
Addressed and kept the html interactive graphs
I don't see dose included in the modeling here, did we decide to skip dose?
Modeled both the simple dose combined with treatment and each dose and treatment as a contributing factor

@gwaybio made changes that we talked about and ready for review. Next PR will be reorganizing the repo and adding viz


Build caching not working in CI workflows

🔎 Search Terms
typescript build github actions caching
🕗 Version & Regression Information

This appears to be consistent across all versions

⏯ Playground Link
No response
💻 Code
n/a
🙁 Actual behavior
In CI, when caching the build directory including the "dist/tsconfig.build.tsbuildinfo" file, a repeated execution of identical build takes the same time
🙂 Expected behavior
Similar to using build cache locally, the build should be instant if no files have been modified.
Additional information about the issue
My suspicion is the build cache relies on modified times of files, and thus is fully invalidated if reused in CI where the repo is checked out fresh every time. Inspecting the tsconfig.build.tsbuildinfo file, I noticed "version" and "signature" on files, as well as "latestChangedDtsFile". I couldn't determine if it was caching on file hashes or modified times fully from this.
I'm not sure if this is expected behavior or not due to the way the caching is done. If its unexpected, I can provide more diagnostics, but I'm assuming it might be expected based on the caching approach. If so, adding an option to cache by file hashes rather than modified times would be valuable for CI caching.

Sounds like a duplicate of #54563.

I think my issue is a bit more generic, and focused on the problem rather than one specific solution. I don't necessarily need a mechanism to determine externally if the project needs rebuild. However, I would like any work already completed by typescript for 99% (or even 100%) of a project to carryover despite timestamps of files changing. I'm imagining something like the cache strategy flag in eslint, which enables CI caching by using file content rather than modified timestamps for better CI support.
That being said, happy to consolidate the discussion on the other issue still, although it seems a bit stale


Great hack. But there is one exception

Love this and it works great.
However, there is one way to bypass this lock that users should be made aware of. Any USB devices connected at boot may bypass this lock. This can be mitigated by first ensuring that the user has full disk encryption enabled to force a password before linux boot and secondly to physically inspect your computer before booting to ensure it has no rogue USB devices connected.

Thanks :)
Indeed, while booting the default option is set to true, thus it will automount everything as a hungry Russian soldier.
Yet, FDE (full disk encryption) won't mitigate it since, the kernel is booted to prompt for a password in order to get the DEK (disk encryption key), at least this is the case for LUKS (Linux Unified Key Setup). Physical inspection would work though :)
I believe that changing the default value will need a kernel recompilation (since not accessible by systemctl), that's why I suggested a crontab as a KISS solution. Perhaps, it's possible with a GRUB customization...
After all, if you don't have a physical control over your PC, pretty nothing will save you :)
Anyway, if you have a solution for the kernel option without a recompilation that would be a great contribution :)


[BUG] PM2-GUI service didn't work at the boot

Hi
I noticed on the V0.1.4, that when I write daemonize = true in pm2-gui.ini file but pm2-gui didn't start from itself.
I tried in command line:
service pm2-gui start
I get that:
pm2-gui.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Any workaround available ? Maybe I have to try some other old version ?
I will let you to tell me what do you think.
Thank you in advance
Regards
PM2 Version: V2.4.0
PM2-GUI: V0.1.4

service pm2-gui start can not work, there is an alternative cmd:pm2-gui start /path/to/pm2-gui.ini


unique biometric ID associated with the fingerprint?

is there a way to return a unique biometric ID associated with the fingerprint?
for example? -
fingerprintAuth.available().then(
        function(avail) {
            fingerprintAuth.verifyFingerprint({
                  message: "Scan with your finger",
                  fallbackTitle: "Enter PIN"
              }).then(function() {
                  console.log("return....unique biometric ID?!"); // how do i return it?
              }, function(error) {
                  console.log("error.....");
              });
        }
)

No. That's not available in the SDKs. Check fi. Apple's docs on Touch ID.

How do we associate the account with the touch authentication?

That's up to you(r app logic). But the bottom line is: only 1 user can use touchid to log in. I'm pretty sure you can't find an app where multiple profiles can log in with their own fingerprints.

@EddyVerbruggen thanks eddy I get you. cheers


Loss names are not equal to the outputs dictionary keys of a model

System information

Have I written custom code: yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10.0.18363
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.8.0
Python version: 3.8.10
CUDA/cuDNN version: none
GPU model and memory: none

Current behavior
The names for the single losses of a multi output model correspond to the output
layer names instead to the output names provided by the keys in the outputs dictionary.
I am not sure if this is the desired behavior.
Expected behavior
I would expect that the names of the losses are the same as the keys in the dictionary
passed to the outputs argument when creating the model.
Standalone code to reproduce the issue
import numpy as np
from tensorflow.keras.layers import Dense, Input
from tensorflow.keras.models import Model

first_input = Input(1)
x = Dense(100)(first_input)
x = Dense(1)(x)

second_input = Input(1)
x2 = Dense(100)(second_input)
x2 = Dense(1)(x2)

model = Model(
    inputs={"first_input": first_input, "second_input": second_input},
    outputs={"first_output": x, "second_output": x2},
)

first_input_data = np.random.random(100)
second_input_data = np.random.random(100)
first_output_data = np.random.random(100)
second_output_data = np.random.random(100)

model.compile(loss="mse")

model.fit(
    x={"first_input": first_input_data, "second_input": second_input_data},
    y={"first_output": first_output_data, "second_output": second_output_data},
    batch_size=2,
    epochs=2,
)

Other info / logs
The loss names are visible in the following logging, when running the code example:
Epoch 1/2
50/50 [==============================] - 0s 673us/step - loss: 0.2440 - dense_1_loss: 0.1308 - dense_3_loss: 0.1131
Epoch 2/2
50/50 [==============================] - 0s 592us/step - loss: 0.1934 - dense_1_loss: 0.0973 - dense_3_loss: 0.0961

The problem is that I cannot see which loss belongs to which single output.
Of course, my real use case is much more complicated, so that I cannot just name the output layers correctly.

Give a name to the output layers:
https://stackoverflow.com/questions/53504813/is-there-a-way-of-renaming-the-metrics-and-losses-of-a-keras-model

@szleb Could you please refer to the comment above and let us know if it helps?
Thanks!

Here is another code example closer to my use case. I hope that makes things a bit clearer
import numpy as np
from tensorflow.keras.layers import Dense, Input, concatenate, multiply, subtract
from tensorflow.keras.models import Model

first_input = Input(1, name="first_input")
x = Dense(100)(first_input)
x = Dense(1, name="model_1_output")(x)

model_1 = Model(
    name="model_1",
    inputs={"first_input": first_input},
    outputs={"model_1_output": x},
)

second_input = Input(1, name="second_input")
third_input = Input(1, name="third_input")
subtraction = subtract([second_input, third_input], name="subtraction")
multiplication = multiply([second_input, third_input], name="multiplication")

model_2 = Model(
    name="model_2",
    inputs={"second_input": second_input, "third_input": third_input},
    outputs={"subtraction": subtraction, "multiplication": multiplication},
)

input_1 = Input(1, name="input_1")
input_2 = Input(1, name="input_2")
layer_1 = model_1(input_1)
layer_2 = model_2({"second_input": input_2, "third_input": layer_1["model_1_output"]})

my_model = Model(
    name="my_model",
    inputs={"first_input": input_1, "second_input": input_2},
    outputs={
        "model_1_output": layer_1["model_1_output"],
        "multiplication": layer_2["multiplication"],
        "subtraction": layer_2["subtraction"],
    },
)

first_input_data = np.random.random(100)
second_input_data = np.random.random(100)
first_output_data = np.random.random(100)
second_output_data = np.random.random(100)
third_output_data = np.random.random(100)

my_model.compile(loss="mse")

my_model.fit(
    x={"first_input": first_input_data, "second_input": second_input_data},
    y={
        "model_1_output": first_output_data,
        "subtraction": third_output_data,
        "multiplication": second_output_data,
    },
    batch_size=2,
    epochs=2,
)

This produces the following log:
Epoch 1/2
50/50 [==============================] - 0s 694us/step - loss: 0.7059 - model_1_loss: 0.1758 - model_2_loss: 0.2769 - model_2_1_loss: 0.2531
Epoch 2/2
50/50 [==============================] - 0s 653us/step - loss: 0.6777 - model_1_loss: 0.1460 - model_2_loss: 0.2485 - model_2_1_loss: 0.2832

Here I do not know any more which loss belongs to the multiplication layer and which to the subtraction layer.
I realised that in the code above my_model.output_names =  ['model_1', 'model_2', 'model_2_1'], but the keys of my_model.output and my_model.output_shape are the custom names ['model_1_output', 'multiplication', 'subtraction']. I also figured out that when the model is created the outputs are ordered alphabetically with respect to the keys in the outputs dictionary (by tf.nest.flatten). So I am able to map the loss names to my output names, e.g. in a customized callback. In the given example this means that model_2_loss refers to the multiplication layer and model_2_1_loss to the subtraction layer. (Correct me if I am wrong.)

You need to use model outputs as a list not a dict:
https://github.com/keras-team/keras/blob/813e6911bd2edd78f85b0c245af6432bdd75cfc7/keras/engine/compile_utils.py#L659-L668

Seems not to solve the problem in this case:
import numpy as np
from tensorflow.keras.layers import Dense, Input, concatenate, multiply, subtract
from tensorflow.keras.models import Model

first_input = Input(1, name="first_input")
x = Dense(100)(first_input)
x = Dense(1, name="model_1_output")(x)

model_1 = Model(
    name="model_1",
    inputs={"first_input": first_input},
    outputs=x,
)

second_input = Input(1, name="second_input")
third_input = Input(1, name="third_input")
subtraction = subtract([second_input, third_input], name="subtraction")
multiplication = multiply([second_input, third_input], name="multiplication")

model_2 = Model(
    name="model_2",
    inputs={"second_input": second_input, "third_input": third_input},
    outputs=[subtraction, multiplication],
)

input_1 = Input(1, name="input_1")
input_2 = Input(1, name="input_2")
layer_1 = model_1(input_1)
layer_2 = model_2({"second_input": input_2, "third_input": layer_1})

my_model = Model(
    name="my_model",
    inputs={"first_input": input_1, "second_input": input_2},
    outputs=[
        layer_1,
        layer_2[1],
        layer_2[0],
    ],
)

first_input_data = np.random.random(100)
second_input_data = np.random.random(100)
first_output_data = np.random.random(100)
second_output_data = np.random.random(100)
third_output_data = np.random.random(100)

my_model.compile(loss="mse")

my_model.fit(
    x={"first_input": first_input_data, "second_input": second_input_data},
    y=[
        first_output_data,
        third_output_data,
        second_output_data,
    ],
    batch_size=2,
    epochs=2,
)

But still the ouptut looks like this:
Epoch 1/2
50/50 [==============================] - 0s 673us/step - loss: 0.5893 - model_1_loss: 0.1533 - model_2_loss: 0.1916 - model_2_1_loss: 0.2445
Epoch 2/2
50/50 [==============================] - 0s 612us/step - loss: 0.5682 - model_1_loss: 0.1377 - model_2_loss: 0.1807 - model_2_1_loss: 0.2498

The problem is that the inner model has two outputs and is used as a layer which covers the names of its output layers. Besides that I actually do use dictionaries on purpose no to depend on any order when defining the models and to get dictionaries when predicting data, so that the outputs can be identified.

I don't know if you can minimize your example a bit but the output names are
print(my_model.output_names)
['model_1', 'model_2', 'model_2_1']

Yes exactly. The ouptut_names are the names of the output layers and not the outputs-dictionary keys (when using dicts). Since the last layer is the model called model_2 having two outputs, the output_names of the model are model_2 and model_2_1.
Whatever the name of model_2 is, I will never be able to identify the two outputs by their loss name. In the example with dictionary you also get
print(my_model.output_names)
['model_1', 'model_2', 'model_2_1']

but
print(my_model.output)
{'model_1_output': <KerasTensor: shape=(None, 1) dtype=float32 (created by layer 'model_1')>,
 'multiplication': <KerasTensor: shape=(None, 1) dtype=float32 (created by layer 'model_2')>,
 'subtraction': <KerasTensor: shape=(None, 1) dtype=float32 (created by layer 'model_2')>}

Why it does not use the dicitionary keys for the output_names when provided? I think that is the point of the problem.
The long code example was just to show that it is not always possible to name the output layers correctly. The issue with the output_names can already be seen in the very first example of this issue.

Ok so this seems similari to https://github.com/tensorflow/tensorflow/issues/34114

changing the method _set_output_names in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/keras/engine/functional.py to something like the following would solve my problem:
if type(self.output) is dict:
    self.output_names = list(self.output.keys())
    self.output_names.sort()
else:
    <<current code>>

Keras now has its own repo so a ticket or PR need to be submited to Keras directly:
https://github.com/keras-team/keras
About this change I have some doubt related to the previous @qlzh727 evaluation:
https://github.com/tensorflow/tensorflow/issues/34114#issuecomment-588538295

Thanks for opening this issue. Development of keras moved to separate repository https://github.com/keras-team/keras/issues
Please post this issue on keras-team/keras repo.
To know more see;
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999
Thank you!

https://github.com/keras-team/keras/issues/16405


Add az-204-no-response-body rule

Adds a new rule to flag a 204 No Content response that specifies a response body.

You can check this rule on the following "current" API definitions in the azure-rest-api-specs repo:

specification/cognitiveservices/data-plane/ContentModerator/stable/v1.0/ContentModerator.json
 1008:22  error  az-204-no-response-body  A 204 response should have no response body.  paths./contentmoderator/lists/v1.0/termlists/{listId}/terms/{term}.delete.responses[204].schema
 1098:22  error  az-204-no-response-body  A 204 response should have no response body.  paths./contentmoderator/lists/v1.0/termlists/{listId}/terms.delete.responses[204].schema

specification/web/resource-manager/Microsoft.Web/stable/2021-03-01/WebApps.json
  7420:22  error  az-204-no-response-body  A 204 response should have no response body.  paths./subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/privateEndpointConnections/{privateEndpointConnectionName}.delete.responses[204].schema
 16572:22  error  az-204-no-response-body  A 204 response should have no response body.  paths./subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Web/sites/{name}/slots/{slot}/privateEndpointConnections/{privateEndpointConnectionName}.delete.responses[204].schema


Add back support for Policy bundles

The data module supports bundled Policies (Policy.bundled_policies field), but the interface and the engine don't implement support for it. Its also unclear still (to me) what the behavior should be for each policy kind (Platform, Constituion, and Trigger).
https://github.com/amyxzhang/policykit/blob/9b728afdcbe92bb0e95eb70f46c9a81b1b526636/policykit/templates/policyadmin/dashboard/editor.html#L221-L224

The point of policy bundles is to chain rounds of voting, because each Policy can only perform one vote. As soon as the policy check returns PASSED or FAILED, the policy execution ends.


Use Shiki code samples and write a blog post saying how to do it

I'd searched a bunch for this before, and people have asked on the shiki issues

Looks good


Node.js  Community Committee Meeting 2020-11-12

Time
UTC Thu 12-Nov-2020 17:00 (05:00 PM):

Timezone
Date/Time

US / Pacific
Thu 12-Nov-2020 09:00 (09:00 AM)

US / Mountain
Thu 12-Nov-2020 10:00 (10:00 AM)

US / Central
Thu 12-Nov-2020 11:00 (11:00 AM)

US / Eastern
Thu 12-Nov-2020 12:00 (12:00 PM)

EU / Western
Thu 12-Nov-2020 17:00 (05:00 PM)

EU / Central
Thu 12-Nov-2020 18:00 (06:00 PM)

EU / Eastern
Thu 12-Nov-2020 19:00 (07:00 PM)

Moscow
Thu 12-Nov-2020 20:00 (08:00 PM)

Chennai
Thu 12-Nov-2020 22:30 (10:30 PM)

Hangzhou
Fri 13-Nov-2020 01:00 (01:00 AM)

Tokyo
Fri 13-Nov-2020 02:00 (02:00 AM)

Sydney
Fri 13-Nov-2020 04:00 (04:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community Committee+Meeting+2020-11-12&iso=20201112T1700
or https://www.wolframalpha.com/input/?i=05PM+UTC%2C+Nov+12%2C+2020+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1Q6wY98rcHPNByREat_lZa5iWaQ4oPw5xdgP9Qu3W8fE/edit

Agenda
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/TSC

feat(charter): introduce emergency and async votes #919

Invited

CommComm Members: @nodejs/community-committee

Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
Notes
The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

Link for participants: https://zoom.us/j/523381536
For those who just want to watch: https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ

Invitees
Please use the following emoji reactions in this post to indicate your
availability.

:+1: - Attending
:-1: - Not attending
:confused: - Not sure yet

There's only one agenda item. Do we want to skip this meeting?

+1 on cancelling as I think we've already discussed the one that is on the agenda.

@bnb just wondering if we are going to cancel or not?

Let's cancel 👍🏻


Reduce public interface MTU when using openvswitch

In order to facilitate path MTU discovery, we should reduce the public
interface MTU to a value that accomodates the overhead produced by GRE
and VxLAN tunnels. For now the proposal is to have a 1450-byte MTU.

We already tell neutron to configure dnsmasq to tell VMs to only use a MTU of 1400 - so what is the additional benefit of this change? and why should it go into mkcloud instead of our product?

I should have added a link to the bug, which has better description:
https://bugzilla.suse.com/show_bug.cgi?id=951345

Additionally, the public interface for the public network should also have the same MTU value. This  helps for traffic incoming from the outside, since the external interface may send ICMP- Fragmentation needed, where the instances may have some filters preventing that and preventing  proper Path-MTU discovery.

This is something to be documented for customers. I don't know how to proceed with that, but for now I'll make a patch for our internal tool (mkcloud) to set that value properly.

Is it docker specific?

May not be Docker specific, but allow me to investigate a bit more, since I cannot reproduce this exact problem in the scenario today.

I have been investigating this issue. I cannot reproduce the exact problem that lead me to propose changing the MTU at the cloud public interface. I have observer other weird behaviors, but for now I'll close this PR.


HTTP Error 500.35-ANCM

Hi ,
So I am using your plugin for a flutter application.
This is my version   oauth2_client: ^1.2.2
I call my API's by building a custom oauth2Class similar to this code here:
class MyOAuth2Client extends OAuth2Client {   MyOAuth2Client({@required String redirectUri, @required String customUriScheme}): super(     authorizeUrl: 'https://...', //Your service's authorization url     tokenUrl: 'https://...', //Your service access token url     redirectUri: redirectUri,     customUriScheme: customUriScheme   ); }
But the apis function properly for sometime but later give an error: HTTP Error 500.35 ANCM Multiple In process Applications in same process. Till where I understand this could be  a server side error.
But my API's and server side codes are correct. Is there anything in the oauth2_client that can cause this? something related to refreshing the tokens?
This API problem get fixed on uninstalling the app and reinstalling it. I highly doubt it can be a server side error .
Could you please tell me any potential causes/bugs that I might have to consider while working with oauth2_client ?

Hi @jainilparikh, I can't think of anything that could cause such an issue.
As you said, it seems a server side error... I suppose you already searched the internet for a potential solution... Anyway, if it can be of any help I found this.
Another thing you could try is updating to the latest version (1.4.1 atm) of the library...

thanks @okrad for clearing my doubt regarding the usage of the plugin . I assume its a server side error itself.


Add test folder to bower ignores

To make package slightly smaller

This change is

 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.

Pull Request Test Coverage Report for Build 2755

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.339%

Totals

Change from base Build 2746:
0.0%

Covered Lines:
720

Relevant Lines:
789

💛  - Coveralls

Thank you for the PR. We keep tests published to bower intentionally, to run  these tests in vaadin-overlay and vaadin-control-state-mixin for all the components depending on them.
See the example here: https://github.com/vaadin/vaadin-overlay/blob/master/test/index.html
Furthermore, AFAIK ignoring has no effect: unlike npm, bower still downloads zip package from GitHub, then extracts all the files except those ignored.
So I have to close this PR, but thank you again for all your contributions! We appreciate it.


Failed to mount component: template or render function not defined

Hello,
[Vue warn]: Failed to mount component: template or render function not defined.
found in
---> <test> at src/html/components/test.vue

I'm getting this error while trying to setup Vuejs SFC's with Blendid.  Here's my task-config:
...
javascripts: {
    entry: {
      // files paths are relative to
      // javascripts.dest in path-config.json
      app: ["./app.js"]
    },
    alias: {
      vue$: "vue/dist/vue.esm.js"
    },
    loaders: [
      {
        test: /\.vue$/,
        use: [
          { loader: "vue-loader" },
          { loader: "vue-style-loader" },
          { loader: "vue-template-compiler" }
        ]
      }
    ],
    customizeWebpackConfig: function(webpackConfig, env, webpack) {
      webpackConfig.plugins.push(new VueLoaderPlugin());

      return webpackConfig;
    }
  },
...

Here's my test.vue component:
<template>
  <div>{{ teststring }}</div>
</template>
<script>
export default {
  data: function() {
    return {
      teststring: "testing"
    };
  }
};
</script>

Also when I update the .vue file Blendid does not seem to be watching it.

same here. Any solutions yet?


"arkmanager installmods" shows useless error msg

Hi!
When running the installmods routine, following errors are shown before downloading the mods:
steam@m1ndfuck:~$ arkmanager installmods
Running command 'installmods' for instance 'main'
[  ERROR  ]     Mod 485734065 is requested but not installed.  Run 'arkmanager installmod 485734065' to install this mod.
[  ERROR  ]     Mod 520879363 is requested but not installed.  Run 'arkmanager installmod 520879363' to install this mod.
[  ERROR  ]     Mod 543859212 is requested but not installed.  Run 'arkmanager installmod 543859212' to install this mod.
[  ERROR  ]     Mod 558079412 is requested but not installed.  Run 'arkmanager installmod 558079412' to install this mod.
[  ERROR  ]     Mod 558651608 is requested but not installed.  Run 'arkmanager installmod 558651608' to install this mod.
[  ERROR  ]     Mod 680481868 is requested but not installed.  Run 'arkmanager installmod 680481868' to install this mod.
[  ERROR  ]     Mod 695990475 is requested but not installed.  Run 'arkmanager installmod 695990475' to install this mod.
[  ERROR  ]     Mod 719928795 is requested but not installed.  Run 'arkmanager installmod 719928795' to install this mod.
[  ERROR  ]     Mod 725398419 is requested but not installed.  Run 'arkmanager installmod 725398419' to install this mod.
[  ERROR  ]     Mod 731604991 is requested but not installed.  Run 'arkmanager installmod 731604991' to install this mod.
[  ERROR  ]     Mod 760884349 is requested but not installed.  Run 'arkmanager installmod 760884349' to install this mod.
Downloading mod 485734065 ... Mod 485734065 downloaded
Copying files to /home/steam/ARK/ShooterGame/Content/Mods/485734065
Mod 485734065 installed
...
(more mods installed)
...

This should be fixed in v1.6.15


poll returns POLLINVAL on macOS

Leading to an infinite busy loop. Discovered here https://github.com/NixOS/nixpkgs/pull/175327 and confirmed using https://github.com/jarun/fastmac.
I didn't dig into this very far, but I found some mention of poll not working on stdin on macOS? Hard to believe. select works (TB_OPT_SELECT). I don't have an easy setup to confirm this. Maybe we switch back to select by default? cc @git-bruh

#include <fcntl.h>
#include <poll.h>
#include <stdbool.h>
#include <stdio.h>
#include <stdlib.h>
#include <termios.h>
#include <unistd.h>

int main(void) {
  printf("%s: %d\n", "POLLIN", POLLIN);
  printf("%s: %d\n", "POLLPRI", POLLPRI);
  printf("%s: %d\n", "POLLOUT", POLLOUT);
  printf("%s: %d\n", "POLLERR", POLLERR);
  printf("%s: %d\n", "POLLHUP", POLLHUP);
  printf("%s: %d\n", "POLLNVAL", POLLNVAL);
  printf("%s: %d\n", "POLLRDNORM", POLLRDNORM);
  printf("%s: %d\n", "POLLRDBAND", POLLRDBAND);
  printf("%s: %d\n", "POLLWRNORM", POLLWRNORM);
  printf("%s: %d\n", "POLLWRBAND", POLLWRBAND);
  // printf("%s: %d\n", "POLLMSG", POLLMSG);
  // printf("%s: %d\n", "POLLREMOVE", POLLREMOVE);
  // printf("%s: %d\n", "POLLRDHUP", POLLRDHUP);

  bool set_term = true;

  struct termios copy;
  int ttyfd = open("/dev/tty", O_RDWR);

  if (set_term) {
    struct termios s;
    tcgetattr(ttyfd, &s);

    copy = s;

    cfmakeraw(&s);

    s.c_cc[VMIN] = 1;
    s.c_cc[VTIME] = 0;

    tcsetattr(ttyfd, TCSAFLUSH, &s);
  }

  struct pollfd fd = {.fd = STDIN_FILENO, .events = POLLIN};

  for (size_t i = 0; i < 2; i++) {
    printf("Poll returned %d\n", poll(&fd, 1, -1));
    __builtin_dump_struct(&fd, &printf);
    getchar();
  }

  if (set_term) {
    tcsetattr(ttyfd, TCSAFLUSH, &copy);
  }
}

This works fine on fastmac, need to narrow down the exact terminal attribute that causes the error
I guess we can do an ifdef for now and set TB_OPT_SELECT if we're on a Darwin host

https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2571

https://github.com/stb-tester/lirc/blob/master/lib/curl_poll.c we can switch to this wrapper instead of spamming if !TB_OPT_SELECT everywhere


fix mongodb engine check

models.py line 315
if settings.DATABASES[connection]['ENGINE'] in ('django_mongodb_engine',):
can throw a KeyError if the project configuration does not follow
Django docs guidelines for setup
Legacy projects can potentially have a working Django app set up like this:
DATABASES = {
    'default': dj_config_url.config(env='DATABASE_URL'),
    'alternative': dj_config_url.config(env='ALTERNATIVE_DATABASE_URL'),
}

Considering that during a migration for simple_history, models.py
checks for a key that does not exist, an exception is thrown that
prevents the project from running.

Codecov Report

Merging #306 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #306   +/-   ##
=======================================
  Coverage   97.62%   97.62%
=======================================
  Files          15       15
  Lines         590      590
  Branches       72       72
=======================================
  Hits          576      576
  Misses          7        7
  Partials        7        7

Impacted Files
Coverage Δ

simple_history/models.py
96.85% <100%> (ø)
: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 b01b92c...dfa67dd. Read the comment docs.

Still an awkward check, but I am okay with this if it prevents some issues.

@singlerider would you like to add yourself to the contributors file before I merge this?

@macro1 Thanks. I added myself to AUTHORS. 👍


OpenMW fails to launch due to morrowind.ini not being correctly capitalized.

Describe the bug
OpenMW fails to launch on a fresh install as it requires Morrowind.ini but a fresh install has a lower-cased morrowind.ini file instead. Manually renaming this file will allow OpenMW launcher to launch properly, after which you can go through the first-time setup process and launch the game, too.
To Reproduce
Steps to reproduce the behaviour:

Install Morrowind via Steam
Select Luxtorpeda as the compatibility tool
Launch game, select openmw-launcher
Game will not launch, silently fails.

Expected behaviour
Have the game and OpenMW's launcher launch without having to manually rename the file.
Additional context
I tested this both on Ubuntu 20.04 (xorg) as-well as Manjaro 20.2.1 (GNOME Wayland), both use a default system filesystem configuration. I am not sure if the issue lies with OpenMW or someplace else, but it might be relatively trivial to look for the configuration file regardless of its capitalization and reference that, as I believe OpenMW supports specifically referencing an ini file.

I believe this is related to #207, your steam cloud save of morrowind.ini is probably lowercase but SteamDB shows it should be Morrowind.ini by default.
https://store.steampowered.com/account/remotestorageapp/?appid=22320
https://steamdb.info/depot/22321/

You're right, it's showing up as lowercase morrowind.ini for me. I have no idea what may have caused it to be this way though. It lists the "date written" is set to the exact date I tried using Luxtorpeda with OpenMW for the first time, although that probably just indicate a last written date, not that it was first uploaded then. I'm not even sure how I can have Steam fix this, it seems like the cloud save functionality doesn't really care about case sensitivity, or it would've overwritten it with a properly capitalized version by now.
I genuinely don't know what could have caused it to be saved in all lowercase. I don't think I have ever tried installing Morrowind under Windows, but perhaps I might have years ago. That'd still not explain why it would have actively renamed the file though, Windows would've simply not cared about capitalization, not forcibly lowercase it. Super weird.

It's most likely because of a Windows or Proton use of the game before, like that Quake example that JoshuaFern linked. The steam cloud most likely has that file saved as "morrowind.ini" even though the actual file in the depot is "Morrowind.ini". I can look into a workaround where we copy that file to the correct name when launching the game.

I've added a workaround here: https://github.com/luxtorpeda-dev/packages/commit/9b353c5dbe7c5c211144fb80e1e9f4279c7eca6e
This would create a soft link if the file is named morrowind.ini. Launching the game again will update to this version. Let me know if you have further issues.


updating mqtt component to handle broker reconnection

Status
READY
JIRA Ticket
SPACON-419
Description

Ensures that the broker can connect on startup, and blocks until it's connected.
Ensures that the broker is connected before publishing a message.
Ensures that when the client disconnects because the server kills the connection, it tries to reconnect to the broker.
Also, add an identifier to the mqtt client so we know which host the server is connecting from

Steps to Test or Reproduce
You can simulate the reconnection by stopping or restarting your mqtt broker.

This needs to be a patch to master.


Bug fixes

Bug fixes on top of #34
(Yea, we really need #25 )

Caught in https://github.com/srid/haskell-template/pull/67


[Bug]: TypeError: no implicit conversion of String into Integer

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
I don't know.
Actual behavior
when writing the Shopify theme dev --store "storeurl" command, can't sync the Shopify theme. It getting this error:
✗ An unexpected error occurred.
        To submit an issue include the stack trace.
        To print the stack trace, add the environment variable SHOPIFY_CLI_STACKTRACE=1.

Verbose output
2023-03-07T18:24:24.065Z: Running command theme dev
  shopify:theme:dev init version<EMAIL_ADDRESS>argv: [ '--store', 'https://club-builder-testing.myshopify.com', '--verbose' ] +0ms
2023-03-07T18:24:24.077Z: Ensuring that the user is authenticated with the Theme API with the following scopes:
[]

2023-03-07T18:24:24.077Z: Ensuring that the user is authenticated with the Admin API with the following scopes for the store club-builder-testing.myshopify.com:
[]

2023-03-07T18:24:24.077Z: Getting session store...
2023-03-07T18:24:24.079Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access"
]
For applications:
{
  "adminApi": {
    "scopes": [],
    "storeFqdn": "club-builder-testing.myshopify.com"
  }
}

2023-03-07T18:24:24.079Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-03-07T18:24:24.079Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.44.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-03-07T18:24:24.739Z: Request to https://accounts.shopify.com/oauth/introspection completed in 654 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"c029af1749c48389d6939b60dc28b4e0"
 - x-request-id: e243142c-95f7-4fb1-a1ea-d375ddf392bb

2023-03-07T18:24:24.743Z: The identity token is valid: true
2023-03-07T18:24:24.743Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-03-07T18:24:24.743Z: The current session is valid but needs refresh. Refreshing...
2023-03-07T18:24:24.745Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_bfdab265737ed4bb73c85a6cc7b02a5fb6a734459947159050d7e3ea11524a31&refresh_token=atkn_0804777e5ed443217ccee41b4a71b3af4745cd7dd42f16e1272e95ee1c5c97d7&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3
With request headers:
 - User-Agent: Shopify CLI; v=3.44.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-03-07T18:24:25.302Z: Request to https://accounts.shopify.com/oauth/token?grant_type=refresh_token&access_token=atkn_bfdab265737ed4bb73c85a6cc7b02a5fb6a734459947159050d7e3ea11524a31&refresh_token=atkn_0804777e5ed443217ccee41b4a71b3af4745cd7dd42f16e1272e95ee1c5c97d7&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3 completed in 555 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"8409d8553fbe737a16a231418485436e"
 - x-request-id: 3a1fb6f9-138f-4a7b-8f1f-b1690b78e206

2023-03-07T18:24:25.305Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=atkn_c9e8bdd70d22fbc55cee8b82db2cc0067dd83cab3eaa8940eabc9a890cb38b82
With request headers:
 - User-Agent: Shopify CLI; v=3.44.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-03-07T18:24:25.306Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=atkn_c9e8bdd70d22fbc55cee8b82db2cc0067dd83cab3eaa8940eabc9a890cb38b82
With request headers:
 - User-Agent: Shopify CLI; v=3.44.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-03-07T18:24:25.720Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=271e16d403dfa18082ffb3d197bd2b5f4479c3fc32736d69296829cbb28d41a6&scope=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.app.cli.access&subject_token=atkn_c9e8bdd70d22fbc55cee8b82db2cc0067dd83cab3eaa8940eabc9a890cb38b82 completed in 412 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"a0475d0fbf5e8d641a07ff8c5e224347"
 - x-request-id: b67cb7f5-6bc2-4716-9a17-79da4aaeb1dd

2023-03-07T18:24:25.956Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=ee139b3d-5861-4d45-b387-1bc3ada7811c&scope=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.storefront-renderer.devtools&subject_token=atkn_c9e8bdd70d22fbc55cee8b82db2cc0067dd83cab3eaa8940eabc9a890cb38b82 completed in 647 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"8687f5c1ba96a7d94578b6a3029054d3"
 - x-request-id: 3946babb-3eb9-46bc-948c-15b23d3358f3

2023-03-07T18:24:25.959Z: Sending POST request to URL https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=atkn_c9e8bdd70d22fbc55cee8b82db2cc0067dd83cab3eaa8940eabc9a890cb38b82&destination=https%3A%2F%2Fclub-builder-testing.myshopify.com%2Fadmin
With request headers:
 - User-Agent: Shopify CLI; v=3.44.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-03-07T18:24:26.440Z: Request to https://accounts.shopify.com/oauth/token?grant_type=urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Atoken-exchange&requested_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&subject_token_type=urn%3Aietf%3Aparams%3Aoauth%3Atoken-type%3Aaccess_token&client_id=fbdb2649-e327-4907-8f67-908d24cfd7e3&audience=7ee65a63608843c577db8b23c4d7316ea0a01bd2f7594f8a9c06ea668c1b775c&scope=openid+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.graphql+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fshop.admin.themes+https%3A%2F%2Fapi.shopify.com%2Fauth%2Fpartners.collaborator-relationships.readonly&subject_token=atkn_c9e8bdd70d22fbc55cee8b82db2cc0067dd83cab3eaa8940eabc9a890cb38b82&destination=https%3A%2F%2Fclub-builder-testing.myshopify.com%2Fadmin completed in 479 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"2362646f37ca75c504dcdd3725ae1414"
 - x-request-id: cd6c48fa-949c-4df8-b71b-2a08b711c48d

2023-03-07T18:24:26.443Z: Setting session store...
2023-03-07T18:24:26.450Z: Getting development theme...
2023-03-07T18:24:27.213Z: Request to https://club-builder-testing.myshopify.com/admin/api/unstable/themes/129076690996.json?fields=id completed in 759 ms
With response headers:
 - content-type: application/json; charset=utf-8
 - x-request-id: 551c279c-0e69-4f09-b313-84ff84a97a8d

2023-03-07T18:24:27.218Z: Ensuring that the user is authenticated with the Storefront API with the following scopes:
[]

2023-03-07T18:24:27.218Z: Getting session store...
2023-03-07T18:24:27.220Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access"
]
For applications:
{
  "storefrontRendererApi": {
    "scopes": []
  }
}

2023-03-07T18:24:27.220Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-03-07T18:24:27.220Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.44.1
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-03-07T18:24:27.231Z: Obtaining the dependency manager in directory /Users/Mac-Mini/Shopify/the-clubroom-shopify-theme...
2023-03-07T18:24:27.238Z:
Running system process:
  · Command: /opt/homebrew/opt/ruby/bin/ruby -v
  · Working directory: /Users/Mac-Mini/Shopify/the-clubroom-shopify-theme

2023-03-07T18:24:27.579Z: Request to https://accounts.shopify.com/oauth/introspection completed in 357 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"8c998fd3bf4abba86f7ff5db8ae897b5"
 - x-request-id: ca7be5bd-b879-4dcd-9692-2e82ba044996

2023-03-07T18:24:27.581Z: The identity token is valid: true
2023-03-07T18:24:27.581Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-03-07T18:24:27.589Z:
Running system process:
  · Command: /opt/homebrew/opt/ruby/bin/ruby -v
  · Working directory: /Users/Mac-Mini/Shopify/the-clubroom-shopify-theme

2023-03-07T18:24:27.605Z:
Running system process:
  · Command: /opt/homebrew/opt/ruby/bin/bundle -v
  · Working directory: /Users/Mac-Mini/Shopify/the-clubroom-shopify-theme

2023-03-07T18:24:27.708Z: Reading the content of file at /opt/homebrew/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/<EMAIL_ADDRESS>2023-03-07T18:24:27.709Z:
Running system process:
  · Command: /opt/homebrew/opt/ruby/bin/bundle install
  · Working directory: /opt/homebrew/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby

2023-03-07T18:24:27.743Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 490 ms
With response headers:
 - x-request-id: d84e615c-493b-4665-b7cf-735e89c84678

2023-03-07T18:24:27.743Z: Analytics event sent: {
  "command": "theme dev",
  "time_start":<PHONE_NUMBER>066,
  "time_end":<PHONE_NUMBER>226,
  "total_time": 3160,
  "success": true,
  "cli_version": "3.44.1",
  "ruby_version": "3.2.1",
  "node_version": "19.7.0",
  "is_employee": false,
  "uname": "darwin arm64",
  "env_ci": false,
  "env_plugin_installed_any_custom": false,
  "env_plugin_installed_shopify": "[\"@shopify/cli\",\"@shopify/plugin-did-you-mean\",\"@shopify/theme\"]",
  "env_shell": "zsh",
  "env_device_id": "5b718c8dc6c226c8c4a6367f78856093065b32dc",
  "env_cloud": "localhost",
  "env_package_manager": "pnpm",
  "cmd_all_launcher": "unknown",
  "cmd_all_topic": "theme",
  "cmd_all_plugin": "@shopify/theme",
  "args": "--store https://club-builder-testing.myshopify.com --verbose",
  "env_plugin_installed_all": "[\"@shopify/cli\",\"@shopify/plugin-did-you-mean\",\"@shopify/theme\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}
2023-03-07T18:24:27.743Z: Completed command theme dev
2023-03-07T18:24:27.885Z:
Running system process:
  · Command: /opt/homebrew/opt/ruby/bin/bundle exec /opt/homebrew/opt/ruby/bin/ruby /opt/homebrew/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/assets/cli-ruby/bin/shopify theme serve . --live-reload hot-reload --theme<PHONE_NUMBER>96
  · Working directory: /Users/Mac-Mini/Shopify/the-clubroom-shopify-theme

┏━━ Viewing theme… ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
┃ DEBUG GET https://club-builder-testing.myshopify.com/admin/api/unstable/themes.json with X-Request-Id: 8f292023-d3a6-4454-9bce-082f0ba1552c
┃ * Syncing theme #129076690996 on club-builder-testing.myshopify.com
┃ DEBUG GET https://club-builder-testing.myshopify.com/admin/api/unstable/themes/129076690996/assets.json with X-Request-Id: d0bbc6ce-c566-4f38-96e8-c6073faba1df
┃ DEBUG ignore package-lock.json
┃ DEBUG ignore package.json
┃                                                   0%
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ (0.88s) ━━
✗ An unexpected error occurred.
        To submit an issue include the stack trace.
        To print the stack trace, add the environment variable SHOPIFY_CLI_STACKTRACE=1.

Error
    at execCLI2 (file:///opt/homebrew/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:55:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Reproduction steps

It worked fine 10 mins before.
I updated the Shopify CLI, restarted my mac
Tried again, can't get success

Operating System
Mac OS Ventura
Shopify CLI version (check your project's package.json if you're not sure)
@shopify/cli/3.44.1 darwin-arm64 node-v19.7.0
Shell
zsh
Node version (run node -v if you're not sure)
v19.7.0
What language and version are you using in your application?
No response

✗ An unexpected error occurred.
To submit an issue include the stack trace.
To print the stack trace, add the environment variable SHOPIFY_CLI_STACKTRACE=1.
Error
    at execCLI2 (file:///opt/homebrew/Cellar/shopify-cli/3.44.1/libexec/lib/node_modules/@shopify/theme/node_modules/@shopify/cli-kit/dist/public/node/ruby.js:55:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Now it's working fine. It maybe my fault. Thanks @Arkham


Any way to set line space?

Hi, does the new 4.0 version support set line space?

@TrustyTechSG what you mean by "set line space"?

Hi @tr3v3r, Sorry for not make is clear, like this, set the space between each row, the Esc/Pos command should be 0x1b 0x33 x

@TrustyTechSG check addFeedLine method. Seems one that you need

@tr3v3r  Thank you for the quick response, yes the feed line can achieve the gap effect I send above, but some time user actually wan to make the line gap smaller to save paper. we have this setting supported in our web receipt printing,  and with native we are currently using our fold version of https://github.com/januslo/react-native-bluetooth-escpos-printer, it has the line space support, but having some issue on the iOS side.

I see.
There is an unexported method addLineSpace

You can raise a PR or I'll try to add it tomorrow.
In the meantime you can try to use addCommand with the HEX command you shared above:
import EscPosEncoder from 'esc-pos-encoder';

let encoder = new EscPosEncoder();

let result = encoder
    .initialize()
     .raw([  0x1b, 0x33 ])
    .encode(); // or any other way to get the Uint8Array

await printerInstance.addCommand(result);

Hope this helps.

Just released v.4.1.0 with the corresponding addLineSpace method exported.
I didn't test it, so please provide feedback on how it works.
https://github.com/tr3v3r/react-native-esc-pos-printer/releases/tag/v4.1.0

@tr3v3r Thank you for the quick update, will try on it and provide you a update tomorrow.

Hi @tr3v3r, just tried installed the latest 4.1.0 version, but Im still facing the error "Could not invoke EasPosPrinterDiscovery.enablelocationSetting" error right after calling the "start" function from usePrintersDiscovery. Do you have any idea what is the cause of this?

This issue is resolved. Please let's discuss the location issue here
https://github.com/tr3v3r/react-native-esc-pos-printer/issues/160


Add essential option

Similar to cpu_shares and mem_limit (which aren't official options for docker-compose.yml, but were added to container transform so they can be outputted in the ECS task JSON definition), we should add the required option, which translates directly to the required option in the TASK definition JSON
Should default to true when it doesn't exist (as it currently does)

Well the cpu_shares and mem_limit are official docker-compose options, see the last point in the yml reference docs.
That being said, I do see the usefulness of specifying a non-compose-standard default: false option in the yml so users wouldn't have to hand-hack \t"default": false, in cases where it would be false. I'll look into it and see if compose doesn't barf with a 'default' parameter and it should be pretty straight forward to add. I'll just need to ensure that a 'default' parameter doesn't make it through the reverse direction, from a task.json to a docker-compose.yml

On a similar note, is restarts essentially the same as required?
In terms of what they mean in the english language, they are definitely not the same thing, but it amounts to the same result. i.e., restarts:true results in the container being restarted should it exist, which is what AWS ECS does if you have required:true

If this were added, I'd suggest using the docker label construct, which can be specified in a compose file. I'm using labels for our deployment to specify stuff like this, and then I transform the task file accordingly.

I think in the interest of keeping the tool more generic, I'm going to reject this idea. It would become really confusing to maintain for support non-valid parameters in multiple formats.

What we ended up doing here is post-processing the outputted task
definition to add the required parameter before sending the definition to
ECS.
On Monday, May 30, 2016, Micah Hausler<EMAIL_ADDRESS>wrote:

I think in the interest of keeping the tool more generic, I'm going to
reject this idea. It would become really confusing to maintain for support
non-valid parameters in multiple formats.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/micahhausler/container-transform/issues/32#issuecomment-222552298,
or mute the thread
https://github.com/notifications/unsubscribe/AAF41b60iBI6N9LXGml8tbC2ZPnXaB5Kks5qG0vagaJpZM4F-GKT
.


Add docs badge to README

Hi there,
I want to propose to add this badge to the README to show off inline-documentation:
The badge links to Inch CI and shows an evaluation by InchJS, a project that tries to raise the visibility of inline-docs. Besides testing and other coverage, documenting your code is often neglected although it is a very engaging part of Open Source that encourages aspiring developers to jump into the source and see how it all ties together.
So far over 600 Ruby projects are sporting these badges to raise awareness for the importance of inline-docs and to show potential contributors that they can expect a certain level of code documentation when they dive into your project's code and motivate them to eventually document their own. I would really like to do the same for the JavaScript community and roll out support for JS over the coming weeks (early adopters are forever, node-sass and when).
Although this is "only" a passion project, I really would like to hear your thoughts, critique and suggestions. Your status page is http://inch-ci.org/github/feross/bittorrent-protocol
What do you think?

Thanks – this is neat. One suggestion: could you make the status page more useful to users of the module? Right now, it seems geared to the module author (me) but I don't think users will find it that useful.


Locations - Bibliographical references in the Graffiti field

Display of bibliographical references in the Graffiti field. Currently, only the cited range appears, but not a link to the relevant bibliographic entry.

(Notes for EM)
Some of the monuments cite graffiti with a bibliographic reference
<desc type="graffiti">Yes (<bibl><ptr target="bibliography.xml#Demestichaetal2017"/><citedRange>376</citedRange></bibl>)</desc>

(See number 2)
and some insert a URL to "historic graffiti" directly
<desc type="graffiti">https://historic-graffiti.cyi.ac.cy/place/6/</desc>

(See number 21)
currently, the indexing XSLT handles the second case, but is unaware of the first case. Will add a test for which format, and the code for bibliography.
Curious if the word "Yes" is necessary. It only appears together with a bibliographic citation, not the Historic Graffiti URL.

Email thread on this issue added so it's all in one place!
From Maria (2024-10-12)
Good-morning.  Since we are using "Presence not verified", perhaps "Presence confirmed" instead of simply "Present" might be an alternative. At Gialia (#16 and #17), because this is somewhat exceptional, I thought to indicate that the graffiti are in Georgian. But, now that you pointed it out and I thought about it, we have graffiti in other languages (e.g. Latin) in other monuments, and this is not indicated, since we are not going into details. So, for the sake of consistency, Georgian should be removed.
From Elli (2024-10-12)
Maria, thank you! It's fine to keep the "Yes", although something like "Present" might be clearer. In one or two cases, there is also some further information, #16 and #17 indicate that they are in Georgian.
I am also asking because I'm trying to make the bibliographic references show up, and need to take into account all the other components that might appear.
From Maria (2024-10-14)
Good-morning.  Since we are using "Presence not verified", perhaps "Presence confirmed" instead of simply "Present" might be an alternative. At Gialia (#16 and #17), because this is somewhat exceptional, I thought to indicate that the graffiti are in Georgian. But, now that you pointed it out and I thought about it, we have graffiti in other languages (e.g. Latin) in other monuments, and this is not indicated, since we are not going into details. So, for the sake of consistency, Georgian should be removed.

Bibliographic references are displaying correctly.
In order for this to process properly, it's necessary to make some a change in the markup of graffiti. I will add this to the MedCyprus documentation.

URLs, such as the Cypriot graffiti reference should be encoded as pointers eg <ptr target="https://historic-graffiti.cyi.ac.cy/place/1/"/> so that they can easily be differentiated from plain text.
ideally, there will only be plain text at the beginning of a graffito entry.
-don't put any punctuation around bibliography such as parentheses around the citations or semi colons in between. These will be supplied by the XSLT.

Long description, for the record:
I made some new Solr fields in order to handle the parts of a graffiti entry more easily. One each for the plain text (index_graffiti_text), one for a URL (index_graffiti_ptr) and one for bibliographic references encoded using the <bibl> element (index_graffiti_bibl). These are handled separately in indices.xsl
Not closed because not pushed yet.

Fixed with f565f7ac1d6a8fbd0d1c0ae7a728389beadfdfad


GDScript bug "constant already exists" in 3.1 (prob related to optional typing changes)

Godot version:
3.1 Alpha 2
OS/device including version:
Ubuntu Linux
Issue description:
With the changes to gdscript to add optional typing, it is throwing an error for constant already exists, even when scoped within another variable such as an enum.
Steps to reproduce:
The following code triggers the error:
enum Forest {
  PATH1 = 5
}

enum Dungeon {
  PATH1 = 5
}

But Forest.PATH1 and Dungeon.PATH1 should be allowed here, as they are scoped within their own enums.
I use this with TileSets in my game, where I use enums to map the tile ids.
Minimal reproduction project:
Attached is a picture showing the bug, as its simple to see in a single file.

Duplicate of #22293 (to be fixed when #19650 is).


Fixes #105

This pull request fixes in popup treeview underscore not showing bug.

thank you for this simple solution as I like them :)


What about the declarations in the "typings" registry and "typed-typings" organization?

What is the plan (if any) for the typings registry and typings already published as npm packages? Also the typed-typings organization?
An example is the chai typings package where DefinitelyTyped has version 3.4.0, but the typings registry has the latest 3.5.0 ( https://github.com/typings/registry/blob/master/npm/chai.json )

We still need to add support for redirect, to match the typings registry features, this is tracked by https://github.com/Microsoft/types-publisher/issues/4.
As for the this specific library, i would recommend moving the latest to definitelytyped.

So, I just realised a clever trick I can start implementing ASAP. I can set the package.json names of repos in @types to @types/<name>. Then, once you install it, it'll automatically be placed in the location TypeScript needs to look it up. That way everything in @types can be supported until redirects are properly implemented.

However, this pattern won't work with the existing approach that uses subdirectories for each version, but it's a good start from the @types org side.


for (teacher contributor) button position need to be fixed

Fixes #1144
Describe the changes you have made in this PR -

fixing for (teacher contributor) button position
make cover image looks like at the prototype

Screenshots of the changes -
At large screens
After

Before

At small screens
After

Before

Coverage remained the same at 84.266% when pulling 69a53089c3a22582a87f403aed7d833bea0d9890 on mahmodHammad:forPos into 4872e6f5d4355054c383207a8ed9e10b6ff1db7e on CircuitVerse:master.

https://github.com/CircuitVerse/CircuitVerse/pull/1152/#pullrequestreview-378099920
DONE!


Create xorg_requirement.rb

This creates a new XorgRequirement class and hacks X11Requirement to defer to it as necessary.
It also removes some hackery from xquartz.rb that just pretended X11 was already installed.
Closes Linuxbrew/linuxbrew#951

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable? Here's an example if you'd like one.
[ ] Have you successfully ran brew tests with your changes locally?

I cannot emphasize enough how much a work-in-progress this is. It works, but telling the various X11Requirement methods to defer to their XorgRequirement counterparts is just awful.
What I think might work better is having XorgRequirement extend X11Requirement and mapping depends_on :x11 to
Nevertheless, submitting the PR so there's a visible indication of my progress.

LinuxbrewTestBot error:
  1) Error:
X11RequirementTests#test_satisfied:
TapFormulaUnavailableError: No available formula with the name "linuxbrew/xorg/xorg"
Please tap it and then try again: brew tap linuxbrew/xorg

I thought that this bug was fixed. =/
See Linuxbrew/linuxbrew#938 and Homebrew/legacy-homebrew#50271

What I think might work better is having XorgRequirement extend X11Requirement and mapping depends_on :x11 to XorgRequirement

:+1:

$ brew install gobject-introspection
==> Tapping homebrew/dupes
Cloning into '/home/sjackman/.linuxbrew/Library/Taps/homebrew/homebrew-dupes'...

It looks fixed to me. I wonder why this requirement doesn't tap. Perhaps because it's in brew tests which behaviours differently than reality some times…

Moved to https://github.com/Linuxbrew/brew/pull/10


Not possible to add funder once the creation plan wizard page is completed

It would be expected that when I first select that I have no funder, but then realise that I have might made a mistake and go back to the plan and edit the 'project details' page and add the funder it will appear here.
However it is not possible to get the drop down menu and even when i type the funder and hit save it remains empty, see below

@mariapraetzellis @briri could you check whether this is an issue on your end too?

This is working for us on our end.

@briri thank you! closing here @raycarrick and opened internal ticket 584


Add home and scratch disk space requirements to project application form.

Description
Can the project application form differentiate home and scratch in disk space requirements, we have some users who store vast amounts of data on scratch but very little on home/groups.

Fixed in https://github.com/tystakartografen/cogs3/commit/49f502bdbc71678bb41fee8514a6b825ca0a4951.


test/lfs-openat: open dfd with O_PATH

This triggers a bug present until at least Linux 5.6.11, causing
EBADF, see https://lkml.org/lkml/2020/5/7/1287
Signed-off-by: Max Kellermann<EMAIL_ADDRESS>

Rebased after @axboe's force-push.


Default Volley from google detected as Volley Plus

About this issue
I used com.android.volley:volley:1.0.0 but it's detected as Volley Plus.
new LibsBuilder()
    .withActivityStyle(Libs.ActivityStyle.LIGHT_DARK_TOOLBAR)
    .withCheckCachedDetection(false)
    .withActivityTitle(getString(R.string.third_party_software_license))
    .withAboutIconShown(false)
    .withAboutVersionShown(false)
    .withAboutVersionShownName(false)
    .withAboutVersionShownCode(false)
    .withFields(R.string.class.getFields())
    .start(this);

I though it's happen because of auto detect read that class
<string name="library_volleyplus_classPath">com.android.volley.RequestQueue</string>
Volley from Google used that class too and have same classpath
Volley Plus should detecting this classpath com.android.volley.toolbox.Volley or com.android.volley.toolbox.VolleyTickle
Details

[6.0.9] Used library version
[27.1.1] Used support library version
[3.1.3] Used gradle build tools version
[3.1.3] Used tooling / Android Studio version
[ ] Other used libraries, potential conflicting libraries

Checklist

[V] Searched for similar issues
[V] Checked out the sample application
[V] Read the README
[V] Checked out the CHANGELOG
[V] Read the MIGRATION GUIDE

they most likely share the same classpath :/
https://github.com/mikepenz/AboutLibraries/blob/develop/library/src/main/res/values/library_volleyplus_strings.xml#L17
any sourcefile which is not existing in volley from google but in volleyplus which can be used to identify?


Issue with running Habitat OVMM

🐛 Bug
Issue with running Habitat OVMM demo
Steps to Reproduce
Steps to reproduce the behavior:
when I run
python projects/habitat_ovmm/eval_baselines_agent.py --env_config projects/habitat_ovmm/configs/env/hssd_demo.yaml provided in the https://github.com/facebookresearch/home-robot/blob/main/projects/habitat_ovmm/README.md, after having the issue https://github.com/facebookresearch/home-robot/issues/476
I got the following error:
pybullet build time: Nov 28 2023 23:52:03 Traceback (most recent call last):   File "/home/ram/repos/home-robot/projects/habitat_ovmm/eval_baselines_agent.py", line 10, in <module>     from evaluator import OVMMEvaluator   File "/home/ram/repos/home-robot/projects/habitat_ovmm/evaluator.py", line 18, in <module>     from utils.env_utils import create_ovmm_env_fn   File "/home/ram/repos/home-robot/projects/habitat_ovmm/utils/env_utils.py", line 13, in <module>     from home_robot_sim.env.habitat_ovmm_env.habitat_ovmm_env import (   File "/home/ram/repos/home-robot/src/home_robot_sim/home_robot_sim/env/habitat_ovmm_env/habitat_ovmm_env.py", line 35, in <module>     from home_robot_sim.env.habitat_objectnav_env.visualizer import Visualizer   File "/home/ram/repos/home-robot/src/home_robot_sim/home_robot_sim/env/habitat_objectnav_env/visualizer.py", line 19, in <module>     from home_robot.mapping.instance.instance_map import InstanceMemory   File "/home/ram/repos/home-robot/src/home_robot/home_robot/mapping/__init__.py", line 5, in <module>     from .voxel import SparseVoxelMap, SparseVoxelMapNavigationSpace   File "/home/ram/repos/home-robot/src/home_robot/home_robot/mapping/voxel/__init__.py", line 7, in <module>     from .voxel_map import SparseVoxelMapNavigationSpace   File "/home/ram/repos/home-robot/src/home_robot/home_robot/mapping/voxel/voxel_map.py", line 17, in <module>     from home_robot.utils.geometry import angle_difference, interpolate_angles   File "/home/ram/repos/home-robot/src/home_robot/home_robot/utils/geometry/__init__.py", line 7, in <module>     from ._base import *   File "/home/ram/repos/home-robot/src/home_robot/home_robot/utils/geometry/_base.py", line 49, in <module>     def xyt2sophus(xyt: np.ndarray) -> sp.SE3: AttributeError: module 'sophus' has no attribute 'SE3'
my python env, got this:
conda list | grep -i sophus sophus                    23.0.1                   pypi_0    pypi sophuspy                  1.2.0                    pypi_0    pypi
Expected behavior
demo should be running without any errors
Additional context

We previously had 0.0.8 version installed. It seems like the library got updated recently. Can you please try updating your sophuspy version to 0.0.8: pip install sophuspy==0.0.8? Please let us know if you run into any other issues.

The issue should be resolved. Feel free to reopen if the issue persists.

My sophuspy is 0.0.8 ,  But still get the error:
home_robot/utils/geometry/_base.py", line 49, in
def xyt2sophus(xyt: np.ndarray) -> sp.SE3:
AttributeError: module 'sophus' has no attribute 'SE3'
Please tell me if you can solve it?

My sophuspy is 0.0.8 , But still get the error: home_robot/utils/geometry/_base.py", line 49, in def xyt2sophus(xyt: np.ndarray) -> sp.SE3: AttributeError: module 'sophus' has no attribute 'SE3' Please tell me if you can solve it?

instead of "import sophus as sp", use "import sophuspy as sp"


problem with client please help

I am new to this client but on the menu at the right it keeps doing whats shown in the photo. I have updated java and reinstalled the client 3 times

Check this -> https://github.com/runelite/runelite/wiki/Disable-Hardware-Acceleration

Duplicate of #1449


Revisit use of Workspace in UI

Refs: #30722
Since we now have a new meaning for Workspace imho we should go through our old uses of workspace in the ui and debate if we should use folder somewhere instead.
Optimally all these actions would update to our new concept of workspace and execute in that context

Yeah we also have settings that use folder vs workspace semantics.

@isidorn is there an entry in your screenshot in particular where you would use "Folder" instead of "Workspace"? I think we decided that we call a single folder workspace also a "Workspace" in the UI as well as a multi-folder workspace. Eventually these two will become very similar once the transition from single to multi folder is smooth.
/cc @sandy081 for input

No, there is no entry in particular where I would prefer using "Folder" over WOrkspace.
However for all tbose entries I would expect that thtey work across folders in the whole MR workspace. IF that is not the case then it can be confusing.

Adding @sandy081 for extensions and @Tyriar for the terminal.

Extensions related commands will be taken care by the issue #29242

Almost all terminal commands work on the active terminal instances. Actual multi-root UX improvements are being considered in https://github.com/Microsoft/vscode/issues/34163


Update gitea?

Hi there
"Updating to a new version
You can update to a new version of Gitea by stopping Gitea, replacing the binary at /usr/local/bin/gitea and restarting the instance. The binary file name should not be changed during the update to avoid problems in existing repositories."
(https://docs.gitea.io/en-us/install-from-binary/)
This seems to be only the previos step before updating, to remove the binary file. (This can't be the update process itself??)
So what i have to do AFTER removing that file? (=The update process itself in my opinion)
Can't see any information related to my issue on https://docs.gitea.io/en-us/install-from-binary/
Thank you for your feedbacks.
Best regards, Jan

well if i understand you are confused that the only step to upgrade gitea is to replace the binary?

Gitea contains migration procedures as part of its code. When you run a new Gitea on an older installation all the needed procedures trigger automatically, provided the previous version was not too old. Gitea maintainers put a lot of effort in keeping backward compatibility as much as possible.
As @6543 said, for a vanilla installation you just need to replace the binary. If you have some custom templates or translations, you'd probably need to take a look at those as well.
What you can't do is to run the binary in a different location or with a different name (e.g. gitea-new) as that would break many things.

thank you very much, will try that.

@martijintro I think that your question has been answered.
I will close this issue so.
Feel free to re-open it if needed.


Modified tar.gz reference name of Design Studio

Modified reference name of Design Studio based on the release name tar.gz.
hcl-dx-design-studio -> hcl-dx-site-manager

 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.


Ability to group factories and move them aorund more easily

Suggestion
So, I create a lot of factory plans using this mod, resulting in my current playthrough of seablock having over 200 different factories, which are also ordered roughly by the type of product they are making. This has resulted in me seeing space for improvement in both the sorting and movement of factories in the list on the left, as well as recipes inside a factory. I'll discuss these proposed improvements here, including how the UI could be implemented.

Allow for moving factories and recipes by dragging instead of clicking on tiny arrows, which can only move exactly 5 steps at the same time. Similarly to how you can drag stations & conditions inside the train schedule manager, I propose replacing the arrows with surfaces that allow for dragging the recipes/factories with sections of vertical striped lines. These could either be on the left as they currently are, or on the right. I'm personally more favourable to the left, so that the factory names can still expand of the screen to the right.

Allow for grouping factories together. The idea is to allow factories to be placed together in a kind of 'factory group'. This factory group has a name, and can be folded in to hide all the factories contained inside, displaying only the name. Adding or removing factories to and from this group can than be done using the drag-and-drop mentioned in idea 1). It should of course still be possible to have factories outside of groups.
The UI I see is having a little arrow between the drag/drop section and the names of these 'factories', which points down if it the 'factory group' is unfolded, with all names being slightly indented to signify membership of the group. Clicking the arrow would instead make it point to the right and hide all the factories inside.

Some of the feature requests mentioned in https://mods.factorio.com/mod/factoryplanner/discussion/637cd9983efc5fe1294a1941 can also be more easily implemented using the ideas described above. If you also make subfloors simply a header that can be folded out individually, and allow recipes/subfloors to be dragged and dropped everywhere, that would easily implement the first two requests. The last request can be implemented by, for example, allowing cross-copy-pasting of factories and subfloors: copying a factory from the list and pasting it in the recipe section of the factory could create a subfloor containing exactly those recipes.

As an additional request: ctrl+click on the 'duplicate factory' button should insert the duplicated factory right beneath the currently open factory, similarly to how ctrl+click works in other places

Hi, thanks for the detailed suggestions!

Dragging is unfortunately not possible within the API, it'd otherwise be the obvious choice.
This is something that's been suggested before, it's sort of like having folders for factories. It's a good idea, but the UI is challenging without drag and drop. What the 2.0 release will have however is a slightly different way to group factories together, maybe that one will work for you.
Yep, but no dragging, :(

The duplicate factory thing is a good idea, implemented for 2.0


[Feature]

Problem
It require a good UI Nav bar as logo floating in left side in all screen look not good.
Description
Site must contain a good nav bar on header

Alternatives

Additional context

Implementation

[x] I would be interested in implementing this feature.

can you assign this issue to me

This issue is the same as #48 so the discussion can be moved over there rather than having two separate issues for the same topic.

Hello, I would like to work on this issue.

Closing as duplicate


Insert-Pointer-Issue in Chrome macOS fullscreen

I have had this insert-pointer-issue throughout the challenges, but I am stuck on challenge 80(Style Text Inputs as Form Controls). I can't insert the pointer to the part of the page I need to add code.

Challenge Name

Issue Description

Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code

Screenshot

Hey @girlboss558 !
This is a duplicate of #7847, there is a work around mentioned there, that you can use, the fix is live on the beta site, but we do not have a date right now for the release to the main website yet.
We request your patience, and apologise for the inconveniences.
Thanks, and happy coding!


Minor fixes

Hello!
Thanks for this repo, I found it very useful. I updated some small details that helped me get things building on my macbook 💃

Thanks!


Moved: Vivaldi.Vivaldi version 3.3.2022.36

This pull request is automatically generated by 🥟 Dumplings
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run


Change Stouts.mongodb version to 2.2.4

The current version of Stouts.mongodb (2.1.11) fail during provisioning.
TASK [Stouts.mongodb : Install MongoDB package] ******************************** fatal: [brain.irma]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'mongodb-org' is available"}
Problem fixed by using the last version (2.2.4).

I tried again this morning. Provisioning passed successfully with Stouts.mongodb (2.1.11).
No explanation :/

Hi @axcheron,
We are very close to remove MongoDB (in favor of JsonB from PostgreSQL) from the whole IRMA project! \o/
See: https://github.com/quarkslab/irma-ansible/pull/144 and https://github.com/quarkslab/irma-frontend/pull/126, two PR merged into testing.
Regards


API new status request

Problem statement: When the secondary is creating or in unhealthy state registrar always shows Activating
We have mentioned below code with status API (https://wavi.ng/status/atsign)
418 - secondary created
200 - Activated
500 - secondary not created
Solution: Show unhealthy state when secondary is unhealthy and Activating when it's actually activating
503 - unhealthy . It will be great if API can return status code as 503 for unhealthy secondary
Registrar need 1 status which will show that secondary was created successfully but now secondary is in unhealthy state.
Linked to https://github.com/atsign-company/at_find_api/issues/27

This issue has caused some confusion recently so am setting priority to High.

@athandle what do you need in order to add this new status to the Registrar?

@gkc @srieteja is working on this. I just need 503 if secondary is unhealthy

deployed to staging at_find_api. Will close this after further testing.

@srieteja any update?

@gkc my changes have been deployed to staging env and I have verified them. They are working as expected. @athandle can provide more info reg deployment to production environment.


Feature-wire/frame | Sabita Shrestha |Module-user-Focused-Data

Learners, PR Template
Self checklist

[ ] I have committed my files one by one, on purpose, and for a reason
[ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
[ ] I have tested my changes
[ ] My changes follow the style guide
[ ] My changes meet the requirements of this task

Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.

@SabitaShrestha325 your work was missed because it had no label. Please label your work with Needs Review, so mentors can find it.
Mentors look at this view to see what work they have to do: https://github.com/CodeYourFuture/Module-User-Focused-Data/pulls?q=is%3Apr+is%3Aopen+label%3A"Needs+Review"


Failing to switch from postgres to influx direct connection

Describe the bug
I have been using Postgres DB for Zabbix and the grafana plugin (works well) - we are migrating to InfluxDB for the longer term storage, when i attempt to switch the zabbix plugin datasource to use influx i get a failed to get metric error in the gui and existing dashboards can't read any data. the influx datasource on its own is indeed working and i can manually pull metrics out just fine. When we enabled Influx on a previous version of the plugin it worked
Expected behavior
The data source should save and test correctly and data should return in dashboard panels
Screenshots

Network data
Grafana Log:
t=2019-08-16T04:09:23+0000 lvl=eror msg="Metric request error" logger=context userId=2 orgId=1<EMAIL_ADDRESS>error="type assertion to string failed"
Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

6.3.3
4.2.5
3.10.4

I've done some debugging further - it would seem that the direct db connection is perhaps not being saved properly in the Database - once i manually updated the DB table (like i did for #731) it actually saved and worked

Hi! Can you confirm this happens in 3.11 as well?

its happening to me still in most current release
doesn't matter if i am switching from Influx to postgres or the reverse - the json_data field in the grafana DB does not get updated properly
specifically dbConnectionDatasourceName does not get updated - the dbConnectionDatasourceId field does get updated though


Form issue during testing

Hi team,
I've been using this custom node for few months and I've been really happy with it.
But following the 0.215.1 release, I'm no longer able to get the node running properly in test mode (using the Test URL).
The page is properly displayed I got a 404 error when submitting my form.
Unfortunately, I don't see anything in our logs on our main process.
Note that the icon is no longer present :cry:
Let me know if you want me to run any test on it.
Thanks

Evening,
Can you try on 215.2, there was a bug with some trigger nodes not listening that has been resolved.

Indeed, the issue is fixed!
Thanks a lot.

No problem, it is nice when issues fix themselves 🙂


Raises floor Go version from 1.17 to 1.18

This moves our floor version to the same we'll release 1.0 with: 1.18. This is congruent with our version policy which is current-2.
Fixes #921

oops windows hates us again. I'll look into it later

yay green on windows finally! I'll squash


Add more tests and refine Intrinsic gas cost calculation

Description:

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (4fdfc26) 76.89% compared to head (b5a61d4) 77.82%.
 Consider uploading reports for the commit 0fcd591 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1774      +/-   ##
==========================================
+ Coverage   76.89%   77.82%   +0.92%
==========================================
  Files          39       39
  Lines        2917     2922       +5
  Branches      584      584
==========================================
+ Hits         2243     2274      +31
+ Misses        497      477      -20
+ Partials      177      171       -6

Files
Coverage Δ

packages/relay/src/lib/precheck.ts
89.02% <ø> (+31.70%)
:arrow_up:

packages/relay/src/lib/eth.ts
85.57% <33.33%> (-0.45%)
:arrow_down:

... and 1 file with indirect coverage changes

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


feat: allow primitive request body in restclient

Current dependencies on/for this PR:

main

PR #5

PR #6   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: f0penGwW85vorg9X6nFC


Floating Player

I want to replicate a similar behavior like this one: https://github.com/advaita13/YouTubeFloatingPlayer Keep video playing in a small view (without stop video in transition). Are there any way to do that behavior?
Thanks

Hi, yes, the YouTubePlayerView is just a View, you can do whatever you want with it.
I remember seeing a library (unfortunately I don't remember its name) implementing the "swipe down behavior" from the YouTube app, you could use that or implement the animation yourself.

Great!! Thanks for you quick response!!

I think this is the library (https://github.com/pedrovgs/DraggablePanel) unfortunately it was deprecated :(

mm it may be. You could try to implement it yourself, it shouldn't be too complicated. You have the example from that library ;)

Yes, I'm working on that! Thanks again

You're welcome :)


Small intro correction in README

Update class count in intro.

This was squash-merged, right? AFAIK GitHub doesn't do fast-forward merges, so a new commit is always created:
Before merge:                  After merge:

                               D (master)
  C (Xymph:master)             | C (Xymph:master)
 /                             |/
B (master)          --->       B
|                              |
A                              A

That is, commit D is always created even if its content is exactly the same as C.
Furthermore, when you pulled the latest changes from the original repo into your fork, GitHub created a merge commit, since the graphs had "diverged" (as far as git can tell) and your fork's commit graph couldn't be fast-forwarded to match the upstreams's graph. So this is what happened:
Before pull:                   After pull:

                               E (Xymph:master)  <-- merge commit
                               |\
D (master)                     D |
| C (Xymph:master)             | C
|/                   --->      |/
B                              B
|                              |
A                              A

I think the best way to avoid this is to submit PRs from dedicated branches in your fork, rather than from master. I suspect that pulling the latest changes from upstream into your fork would then not create merge commits, but simply fast-forward your graph to include the new upstream commits.
For now, the best way to resolve things is to force-set the master branch in your fork to point to the same commit as upstream master:
git branch -f master 3c8833a

That should get the graphs looking like this:
D (master) (Xymph:master)
|
B
|
A

Hope this helps! Let me know if there's anything I should clarify.

TBH, I don't recall how I committed/merged the README change in March, but I definitely didn't create a branch for it in my local repo (didn't seem worth the trouble for a one-word change). Advice noted about doing that in the future.
And {sheepish grin} I guess I just made it worse by hastily merging and pulling #98 before resolving this here problem. The git command is denied with "Cannot force update the current branch".
I wouldn't mind deleting my entire fork and starting over, if that is the easiest way out by now.

The git command is denied with "Cannot force update the current branch".

I don't think that's related to the merge of #98. I believe git might not allow you to force-update the current branch. If I'm correct, this should work:
$ git checkout HEAD            # "Step out" of the `master` branch
$ git branch -f master c48284c # Note: the ref is no longer 3c8833a since the merge of #98.
$ git checkout master          # Step back into `master`

The first checkout warns: "Your branch is ahead of origin/master by 4 commits."
The branch command gives the same fatal error as before.
The second checkout says I'm already on 'master'.
Does that help?

It does, sorry. I misremembered that git checkout HEAD does not actually get you into detached head state. Try git checkout HEAD~ instead as the first command. That will put you on a commit other than the tip of the master branch, and then you should be able to force-update it since you're no longer "sitting" on it.

Thanks, now it worked, and master and my graphs are clean.  :)
I'll try not to get myself in this kind of trouble again.
(not making promises about other kinds...)

I'm glad it worked! It was good for me as well to brush up on some concepts :)
By the way, I always recommend this talk ("Git For Ages 4 And Up") which helped me build intuition for git's graph. Once the model is clear in your head, it becomes possible to translate obscure-looking commands into "physical", visual operations in a graph. git log --graph is also crucial to understand the state of the repository.

Yes, I viewed that when you first recommended it (and parts of it again later), but after all this time it has faded into memory a bit, and understanding what was wrong with my repo wasn't so trivial anymore. Thanks again for your time.