feat: add warning when using fallback font

Print a warning message when no font is selected and we are using heuristic method to select font.
This typically happens when inputing chinese characters without setting specific font.

🤔 seems that test runner is not happy with new warnings. Any idea to fix this?

This does not work as intended because before select_fallback is invoked, an explicit list of fallback fonts is used.

seems that test runner is not happy with new warnings. Any idea to fix this?

I think this doesn't work as intended because before select_fallback is invoked, a well-known list of fallback fonts is traversed, which don't trigger the warning.

Agree. It's missing. It would be better if this can also trigger the warning. But it seems that the usage of that list is somehow scattered everywhere in the code, so I didn't change it. Currently it can only produce warning when all the list is used up, like inputting Chinese characters without setting other fonts.
I can move the code which add the well-known list into consideration to select_fallback if it is desired.

I am not sure whether the book is really the best place to emit the warning or not.

idk either. I feel awkward when adding tracer: TracedMut<Tracer>, span: Span everywhere in the code path. Which place do you prefer? I'd be happy to change the code if there is a better option.

I am worried about warning spam if there is a large amount of text with fallback. We might need configuration to enable/disable this, e.g. fallback: false | "warn" | true.

Yes. We should provide a way to silent warnings. And warnings should be enabled by default.

I think that the warning for family & style/weight/stretch need to be considered in whole, especially regarding configuration. Do we want to warn if weight 500 is requested, but only 450 exists? If italic is requested, but only oblique exists?

It's hard. I think we can add warning to this as long as user can suppress it. This can help user find problems with their font config.

The error messages itself should be lowercase and not use debug formatting, but I guess that's WIP

Yes, it should be improved.

I also want to note that just adding an emoji will already trigger this warning as few people will explicitly list an emoji font in the fallback chain. One might argue that this is reasonable behaviour for a typesetting system, but at the same time it feels like bad ergonomics.

We might need configuration to enable/disable this, e.g. fallback: false | "warn" | true.

Would it make sense for there to be a compiler flag for the level of warnings displayed? Personally I'd love to be inundated with warnings, but others might not want to see them at all.

In general I think we could wait for warning suppression to land. I believe there isn't an issue for that, so we could open it.

In general I think we could wait for warning suppression to land.

IIUC it wouldn't land in weeks or a few months. And there is a lot of design work to do. But the font matching problem is already causing many problems. New users keep asking "doesn't typst support bold?" or "Why does typst choose X as the default Chinese font?".

IIUC it wouldn't land in weeks or a few months. And there is a lot of design work to do. But font matching is already causing many problems. New users keep asking "doesn't typst support bold?" or "Why does typst choose X as the default Chinese font?". I think adding a warning atm would yield better UX.

It's true that it will take a while (unless we take action now). But the alternative is to have users inadvertently stuck with warnings in their documents they can't get rid of, such as when using emoji or certain symbols, as Laurenz mentions. So, ideally, we'd use a unified system for toggleable warnings so we can add a ton of them - not just for fallback fonts.

They can get rid of the warning using options: fallback: false | "warn" | true. maybe a 1-liner: `#set text(fallback: false).
As for the "unified warning", can we simply add a warning filter arg or something like -wall to disable warning?

I've posted some thoughts about warning supression and spam in the discord forge. In particular, I am now of the opinion that we

should not have fallback: "warn" but rather opt for a more unified interface.
should have a system for grouping warnings, so that all font fallback warnings are grouped together by default

currently i'm on LNY vacation. i will give a more detailed design later.

Someone else also started looking into this and asked a few questions, the answers to which might also be relevant here.

Maybe i will close this since I have no plan continue working on this in near future


Add temporary connection - like a normal connection but between a node and a point in space

The purpose of this type of connection is to visualize where the edge is being dragged to while it is being dragged. I will post test code for this later, which demonstrates how to use it.

I'll give it a try soon!


verifyIdToken()

From my front (React) I get tokenId (rawToken.....) with msal.js;
I want to send this to my ServerApi(NodeJs) endpoint and

verify this tokenId with my appId (and secret if needed)
get profile informations
do my logic of login...

FYI accessToken = Null // InFront
Question : After some research I find that probably I need to use @microsoft/microsoft-graph client, but I didn't find how to verify my tokenId ?
for example google-auth-library provides a function(OAuth2)
named verifyIdToken make me able to do this kind of staff

Thanks for your interest @FridMehdi. This repository isn't a good place to ask support questions, you really should ask these kinds of things on Stack Overflow. However, I'll share my two cents :).
This actually would not require Graph at all. You're looking for the Microsoft Identity platform. The docs are all there on verifying ID tokens, etc.
If you did want to call Graph from a backend while the users login with your front-end, you would want to look at the on-behalf-of flow.


Add Modeler and further improvements

Closes #2
Closes #44

Add Editing feature
Overwork project structure
Add OS support for Windows
Change icons

@salaboy Saving changes in the Editing Panel only works via the button. It would be possible to do it on every changing action, but want to control it by now. We can open another issue for that.


Workflow fails for pull requests from forks

The workflow fails when creating a pull request from a fork repository to an upstream repository.
Perhaps the error occurs because the correct branch name is now used in #70, and the branch cannot be found in the upstream repository where the workflow is to be executed.
The workflows where this problem has actually occurred following:
https://github.com/jaoafa/jaoweb4/blob/847e0875f9ae88cd69125433cfbfedfd9c33d753/.github/workflows/publish.yml#L98
The actual problematic workflows resulted in the following:
https://github.com/jaoafa/jaoweb4/actions/runs/5296316660/jobs/9587342658
For pull requests from forks, it is preferable to use SHA. Alternatively, it would be possible to change this in inputs.

I have the same problem. Trying to build PR'a to a dedicated preview site, but getting missing API key error.

@marvin-hansen Hi, Your problem may be slightly different from what Hiratake san problem is.
I think your workflow is this file: https://github.com/deepcausality-rs/sites/blob/24f7e37c0092f534bd820dd1e8ba9dc10f9f3f1e/.github/workflows/preview.yml
The CLOUDFLARE_API_TOKEN secret is required, did you set it and run it?
Since the error is Input required and not supplied, I assume that the value for apiToken does not exist...😢
If the problem is the same as Hiratake's, the error should include a statement like No ref found for!
I hope you will find it useful!

Well,
I did provided the token but upon further investigation, it became clear
that there are a number of issues related to accessing GH secrets from a PR
that originated from a forked repo. I tried a few suggestions, but nothing
worked out so I’m not sure where to go from here.
Best
On Mon, Sep 11, 2023 at 9:27 PM Tomachi @.***> wrote:

@marvin-hansen https://github.com/marvin-hansen Hi, Your problem may be
slightly different from what Hiratake san problem is.
I think your workflow is this file:
https://github.com/deepcausality-rs/sites/blob/24f7e37c0092f534bd820dd1e8ba9dc10f9f3f1e/.github/workflows/preview.yml
The CLOUDFLARE_API_TOKEN secret is required, did you set it and run it?
Since the error is Input required and not supplied, I assume that the
value for apiToken does not exist...😢
If the problem is the same as Hiratake's, the error should include a
statement like No ref found for
https://github.com/jaoafa/jaoweb4/actions/runs/5296316660/job/14339062309#step:8:14
!
I hope you will find it useful!
—
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/pages-action/issues/94#issuecomment-1713883953,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFYR7XF2YXHIOPGBIYS4633XZ4GVFANCNFSM6AAAAAAZKFANPA
.
You are receiving this because you were mentioned.Message ID:
@.***>

For reference, take a look at the following workflow! ❤
https://github.com/jaoafa/jaoweb4/blob/2b337c1a15385454f2aa6f5c07f6af95d1d680f9/.github/workflows/publish.yml#L18

@book000
I'm struggling a bit to make the GH action you shared work.
Good news is:

Auto-comment that a PR from a forked repo needs the 🚀request-deploy label works

Once the label has been added, the publish action runs. Nice.

Now, my page is a Hugo static page  and the lock.json is in the folder separate folder called web. Therefore, I added the  working-directory tag and npm ci installs.
The npm run generate steps also gets the working-directory.
      - name: Run generate
        working-directory: web
        run: npm run generate

However, this steps fails in the CI
Run npm run generate
  npm run generate
  shell: /usr/bin/bash -e {0}
npm ERR! Missing script: "generate"
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/[2](https://github.com/deepcausality-rs/sites/actions/runs/6221068467/job/16882331675?pr=57#step:7:2)02[3](https://github.com/deepcausality-rs/sites/actions/runs/6221068467/job/16882331675?pr=57#step:7:3)-09-18T10_07_[5](https://github.com/deepcausality-rs/sites/actions/runs/6221068467/job/16882331675?pr=57#step:7:6)5_3[8](https://github.com/deepcausality-rs/sites/actions/runs/6221068467/job/16882331675?pr=57#step:7:9)1Z-debug-0.log
Error: Process completed with exit code 1.

The complete workflow file:
https://github.com/deepcausality-rs/sites/actions/runs/6221076223/workflow
And the last failed run:
https://github.com/deepcausality-rs/sites/actions/runs/6221076223/job/16882354763?pr=57
Any idea how to fix this?

I think the correct way to build HUGO sites manually is something like this:
hugo --environment production --gc --minify
Have to update the action to install & run hugo

@marvin-hansen
npm run generate runs scripts.generate in package.json. Therefore, if the generate script is not defined, this error will occur.
For a simple solution, replace this part with the following:
      - name: Build hugo site
        working-directory: web
        run: hugo --environment production --gc --minify

thank you @book000
I'm working on it.
The theme I am using can actually be build with npm using install & build. I just tried it locally and that one worked.  Trying it now on CI
npm install
npm run build

@book000 This one worked. The last blocker I solved was to enable submodule checkout so that the theme gets cloned as well.
Now it's all running.
https://github.com/deepcausality-rs/sites/actions/runs/6221806137/job/16884805932
Thank you so much for all your help.


Calculations

Implemented logic modules, didn't import the calculate function to App yet to avoid linter problems.

Thanks @zenott , I am still working on the integration tests because I still catch bugs!
But I will merge and continue testing in the final milestone to have better access to the UI.


Add pod failover scenario to run all pods on same node

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.4%) to 53.36%

Totals

Change from base Build<PHONE_NUMBER>:
1.4%

Covered Lines:
262

Relevant Lines:
491

💛  - Coveralls


Allow full 256 color ansi palette + italic, underline in toml and nix.

I wanted to use the full ansi color palette plus italic and underline in motd, plus I wanted to use it from TOML. This enables such usage through replacement strings. In the case of colors the replacement strings are just "{<color_number_here>}" while for bold, reset, underline and italic they are "{bold}", "{reset}", "{underline}" and "{italic}" respectively.
A toml example would be:
[devshell]
name = "ansi"

motd = """

{bold}{102}ANSI{reset}{102} - who doesn't like colors?{reset}

"""

@zimbatm I believe it's ready now.

thanks!


DELETED

DELETED

DELETED

What is this issue about?

Sorry for the mess, just found out, that it was my fault. Was confused by error output referring to internal chat's module. Couldn't delete the issue... :(

it's ok Thanks


Remove Monolog logging

In phpDocumentor 3 we want to simplify the concepts and enable people to contribute sooner. In order to do this we need to take multiple steps and one of them is remove the log to file feature of phpDocumentor.
The current implementation of logging is hardly ever used as far as I can determine and only pollutes the codebase with calls to Monolog and with specialized code to read from the configuration and command line.

Resolved in #1563


Azure availability map may be incorrect

Issue in ./help/implementation-playbook/infrastructure/cloud/regions.md
https://experienceleague.adobe.com/docs/commerce-operations/implementation-playbook/infrastructure/cloud/regions.html?lang=en#azure-regions
The Azure availability map is different (showing more availability zones) to the one provided on Field Readiness https://fieldreadiness-adobe.highspot.com/items/5f1885ada4dfa07661acaa35?lfrm=srp.5#3
Jay Chaudhury advised that FR is the accurate source which he updates, so the public page may be inaccurate and need a revision.
It is also ambiguous what 'potential availability zones' means, or the 'local' zone marked on the AWS map means - will be worth updating to a clearer statement

@adobe export issue to Jira project COMDOX as Story

Updated in https://github.com/AdobeDocs/commerce-operations.en/commit/5889b5757d02823750c92c5ef561e5f1aa1ad67f. Will be deployed to production shortly.


StatusCodeError: 400 You need an email or confirmed phone number

Hey i have this message error StatusCodeError: 400 - {"message":{"errors":["You need an email or confirmed phone number."]},"status":"fail"} (if i print getProfile() for example that going to work)
i just tried to take the example, but impossible to update the profile

const Instagram = require('instagram-web-api');
const username = 'myusername';
const password = 'mypassword';

const client = new Instagram({ username, password })

;(async () => {
    await client.login()
    const profile = await client.getProfile()

    await client.updateProfile({ biography: '❤', website: 'https://jlobos.com/', gender: 1 })

    console.log(profile)
  })()

Does your account have a confirmed e-mail/phone number?

Yeah my account have a confirmed email

I have the same problem

I have the same problem

This api must be outdated


outsideClick trigger does not hide popover when clicked outside

Bug description:
After updating from 1.3.3 to 2.0.1 I noticed that outsideClick trigger does not hide the popover anymore when clicked on something outside of it.
Link to minimally-working plunker that reproduces the issue:
https://plnkr.co/edit/GW18A5P9Rm3aNvIgzQ5C
Version of Angular, UIBS, and Bootstrap
Angular: 1.5.8
UIBS: 2.1.3
Bootstrap: 3.3.6

You should change popover-trigger="outsideClick" to popover-trigger="'outsideClick'"

Oops, thank you very much.

That solution works, but that is really lame.  It's not clear at all from the docs that a literal string needs to be passed in.

i think this is because you can declare multiple triggers, i.e. tooltip-trigger=" 'mouseenter' 'outsideClick' "


Creating a v1.2.0 release

Hello, I see there's a v1.2.0 commit, would we be able to get a new release published to npm? Thanks!

@kalmecak I already drafted the release on GitHub, if you don't mind could you save it and then publish to npm as well? Thanks

Yes please.... Do this.

I think this issue can be closed. I see v1.2.0 on npm (published on April 16, 2020).


check that readers passed in are valid when they are passed in

I'm not exactly sure how that would work, but see https://github.com/serratus/quaggaJS/issues/360#issuecomment-579480829

JavaScript is a non-typed language, and if you start with that approach, to be consistent, why don't type check EVERYTHING? that's a bit of overkill in my opinion...
So, I'm not sure that this feature is needed, since that's extra runtime check, while you can use TypeScript to solve that problem...

Well, there's a specific list of valid readers, and if you pass in something that isn't valid at init time, then sometime later, you get an error that doesn't appear to be at all related to what you passed init.  That's a pretty bad experience, IMO.  That list also could be a dynamic list, with the support I've added for external reader modules .. and once that is working fully, I'd like to remove the built-in readers to separate modules, so that we don't have to ship the code for all readers in the bundle, and it'll also prevent people from making the common mistake of enabling all readers.
I think it would be good to throw in init, or at least warn in init, then ignore the bad reader, so it doesn't trigger errors at a place that is completely irrelevant to what the error is.

This list? I'd would throw a hard error in init() if an unknown reader is configured.

Yep that's the one.  I had filed this when I ran across the problem, just for future reference, I hadn't really thought about it at the time ...
But now that we're discussing it :-)  I'm wondering if it should match the readers in init() into the list, subtract any that are not valid, then throw if there's no valid left -- or if it should just throw if you pass in any invalid ones.
Method 1: If you pass in multiple readers, but only 1 of them is invalid, the others work, without it breaking the entire thing.  Downside is that if you don't check the log, you have no idea why the invalid reader isn't working.
Method 2: It just straight up fails, and you fix your broken init() :-)
I'm leaning towards #2 because this is a library that is targeted towards devs, rather than an end-user application, where i'd want to try to figure out what the user meant if possible.

I would totally go with method 2.
Better show the dev directly the mistake instead of "hiding" it.
Will that work with dynamic reader list? I assume that those have to be registered upfront somehow and that you can then check against ... I don't know, some kind of identifier?

Yeah, it should.  Dynamically added readers don't seem to be working in LiveStream mode, so that's a problem (and also quite difficult to write a test for, I think, but it might be possible that ImageStream can be handled and used to substitute for it..) so there might be some changes in how those get registered.. but right now, you call registerReader before you call init() and it should add it to the list.
I think once I'm done converting them all to typescript, I'm going to take the UPC reader as it's 100% known functionality, and test it as a plugin.

What I was saying is, if you want to write consistent code, why would you only check the reader list? Why stop there and don't check the rest of the configuration?
Checking only the readers but not the rest looks like a half-ass solution for me.
So, if we want to have a consistent library, there are two options:

Check the whole configuration
Check nothing and rely on other ways (i.e. check on compilation time with TypeScript)

The problem of the first approach is that you require more code and more execution (because it's done in run time) and that's an overhead, which might not be useful for everyone (i.e. for us using typescript).
It would be something similar to prop-types in React, which I used to use a lot, but I stopped using it on favor of TypeScript strong-typed projects.
Also one thing to consider, is having different builds for production and development, so the checks are only done in development, without including any code in production. That's also a valid approach which doesn't add overhead in production. And if you don't use test in development you are doing it just wrong :)

Not all people build quagga themselves. They just use the pre-built dist.
That might sound totally wrong to the full-hearted frontend dev, but is reality.
They will likely not switch between dev and prod built.
Additionally: wrong spelled configuration shouldn't be a problem during runtime, while a misspelling in the readers name is.

... i just had another thought, that it might even be a better idea to change init() so that readers is BarcodeReader[] rather than string[] .. does that seem weird?

Not at all and I could work with both. But to be devils advocate here: this is a library and you should think of the users that are not frontend devs. If there will be a solution to still drop the prebuilt file(s) into the assets directory and use this new style in init() without setting up a complete built-stack then it is "only" a massive BC break.
My wish: please don't force anyone into needing a mandatory frontend built-environment.
Had a quick look at initReaders() and the constructors of the readers. Half of them take opts and supplements as arguments. Can those params be moved  easily to the userland?

I think the crux of this problem, is that passing invalid reader strings generates a runtime error -- after the fact -- that doesn't point to where the actual problem is.  Screwing up the configuration in most other ways, probably just ends up with an incorrectly configured setup.  That is the difference between doing a runtime validation on the readers versus the rest of the configuration.    I guess I'd have to go and write an init() with a bunch of incorrect parameters to test that theory, but in either case -- the library shouldn't blow up in a way that points to code inside it failing, if it's userland that's wrong.
There's already this setup that i inherited, that readers can be either string[] or object[] where object includes the name, the opts, and the supplements.  Using a BarcodeReader class instead of a string name for those could be a new option, that would both be easily checkable (!instanceof BarcodeReader) and might not require any pre-configuration (Quagga.registerReader before Quagga.init)
This is future, anyway, I think my priorities when I do have time to work on this right now are:
TypeScript
Automated Testing
Re-implement Workers


broadcast only tunable parameters

We want to broadcast only the parameters that are used in tuning. Other parameters like "imageLoader" may not be required, and throw error if they are not pickle-able.
To do this, we use the tunable_params that we already used to validate params, it has been sent to the constructor, and is also used at the time of broadcast.
To test this, we ran the local tests, could not run the local-cluster test since it does not support pyspark (thanks for help, Lu Wang). To test on cluster, we used Databricks clusters.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #120   +/-   ##
=======================================
  Coverage   85.38%   85.38%
=======================================
  Files          33       33
  Lines        1923     1923
  Branches       44       44
=======================================
  Hits         1642     1642
  Misses        281      281

Impacted Files
Coverage Δ

...n/sparkdl/estimators/keras_image_file_estimator.py
88.97% <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 9f05fc2...6f39536. Read the comment docs.

cool. lgtm as well. feel free to merge once the tests pass @smurching


tf.keras - Saving model ignores layers that aren't fed into other layers

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): b'v1.11.0-rc2-4-gc19e29306c' 1.11.0
Python version: 3.6.7
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
When I save and reload a model that has multiple inputs, but some aren't fed into any layers (they are used in a custom loss function), not all inputs are created in the new model.
Opening the HDF File of the saved model shows that the input layers aren't saved in the model configuration.
Describe the expected behavior
All layers should be correctly created
Code to reproduce the issue
import tensorflow.keras as keras
import numpy as np

def custom_loss(loss_input):
    def loss(y_true, y_pred):
        return y_true * y_pred * loss_input
    return loss

# Create simple model
input_layer = keras.Input(shape=(1,))
loss_input_layer = keras.Input(shape=(1,))

output = keras.layers.Dense(1)(input_layer)

model = keras.Model(inputs=[input_layer, loss_input_layer], outputs=[output])

model.compile(optimizer=keras.optimizers.Adam(lr=1e4), loss=[custom_loss(loss_input_layer)])

# Train the model with some example data
input_data = np.random.random_sample(512)
loss_data = np.random.random_sample(512)
output_data = input_data * -1

model.train_on_batch(x=[input_data, loss_data], y=[output_data])

# Save and load model
model.save("test.h5")
model = keras.models.load_model("test.h5", custom_objects={"loss": custom_loss(loss_input_layer)})

# Test model
model.predict(x=[[np.random.random_sample(1)], [np.random.random_sample(1)]])

Other info / logs
Traceback (most recent call last):
  File "C:/Users/user/test/testTensorboard.py", line 31, in <module>
    model.predict(x=[[np.random.random_sample(1)], [np.random.random_sample(1)]])
  File "C:\ProgramData\Miniconda3\envs\SolitairePPO\lib\site-packages\tensorflow\python\keras\engine\training.py", line 1752, in predict
    x, check_steps=True, steps_name='steps', steps=steps)
  File "C:\ProgramData\Miniconda3\envs\SolitairePPO\lib\site-packages\tensorflow\python\keras\engine\training.py", line 993, in _standardize_user_data
    class_weight, batch_size)
  File "C:\ProgramData\Miniconda3\envs\SolitairePPO\lib\site-packages\tensorflow\python\keras\engine\training.py", line 1112, in _standardize_weights
    exception_prefix='input')
  File "C:\ProgramData\Miniconda3\envs\SolitairePPO\lib\site-packages\tensorflow\python\keras\engine\training_utils.py", line 286, in standardize_input_data
    str(len(data)) + ' arrays: ' + str(data)[:200] + '...')
ValueError: Error when checking model input: the list of Numpy arrays that you are passing to your model is not the size the model expected. Expected to see 1 array(s), but instead got the following list of 2 arrays: [array([[0.08552315]]), array([[0.11069975]])]...

Nagging Assignee @ymodak: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

It looks like a bad written code. If you call model.summary() before saving it, you'll not see no second input in it. It is ignored because disconnected from other layers. Check keras guide for multi-input model for the right implementation. The basic idea that you use keras.layers.concatenate to merge two inputs and then split them in loss function.

In this example, the inputs can be merged, but that is not always the case, for example when the inputs different shapes.

Apologies for the delay in response.
I was able to execute your code snippet successfully using TF 1.13.rc0
Can you please confirm? Thanks!

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


add sonar back as prow one is having issues

Related Issue: [closes|resolves|fixes] open-cluster-management/backlog#<ISSUE_NUMBER>
Description of Changes

[ ] I wrote test cases to cover new code

/hold

close as prow will have unit test & sonar test output


BLE Error after enabling nvs encryption (CON-882)

My Application is using the BLE commissioning after powering up. Before i activated nvs encryption it was working fine. Even with activated flash encryption there is no problem which lets me think that i've nailed it down to the nvs encprytion.
I have only one nvs partition named "nvs" and one nvs_keys partition. The nvs itself is working correctly with activated encryption. Beside my custom data i am using the nvs partition for the matter certificates (factory data).
With activated nvs encryption the BLE is throwing the following errors and the commissioning window is never opened:
E (5831) chip[DL]: Configure Adv Data failed: Error Device Layer:0x000002
E (5841) chip[DL]: Disabling CHIPoBLE service due to error: Error Device Layer:0x000002
E (5851) chip[DL]: Long dispatch time: 1501 ms, for event type 2

The full logs:
full_logs.txt

ESP-Matter Commit Id: b09277eba25e0978cac9ca926daba9d6b225f707
ESP-IDF Commit Id: e088c3766ba440e72268b458a68f27b6e7d63986
SoC: ESP32

Solved it by generating and flashing nvs_keys and the encrypted nvs image on my own. In my thought the nvs encryption of existent data was done by the application on first boot, but it wasnt and this was causing the problem.


Feature Request: two ** allowed

Hi.
Thanks a lot for creating this tool!
I have an idea for a future feature, let me know what you think on this.
Setup:
I'm using dpath version 1.4.2 in Python 3.6.8.
Current Behaviour:
import dpath
d = {'1': {'2': {'3': 'c'}}}
dpath.util.search(d, '**/2/**', yielded=True)

results in
InvalidGlob: Invalid glob. Only one '**' is permitted per glob.
Desired Behaviour:
It would be nice to have support for two **, such that also multiple recurrences of the same key (e.g. if there were two '2' as keys) would be found.
So for the above example the output would be:
('1/2', {'3': 'c'})
('1/2/3', 'c')

I presume there is a good reason for why this is not available; could you shortly explain the reason? Is there a workaround?
Thanks for your response in advance.
Have a nice day.

The issue here is that star-star is handled by expanding the single star-star into a series of single stars such that the length of the glob and the path match. If we allow multiple star-star, then this becomes a combinatoric problem where each possible expansion of the star-star has to be produced. While it is possible to do it it would easily produce problems with cpu and memory usage.
For your specific example, it may be sufficient:
import dpath.util

d = {'1': {'2': {'3': 'c'}}}

twos = dpath.util.search(d, '**/2', yielded=True)
for (p, v) in twos:
    print((p, v))
    for (sp, sv) in dpath.util.search(v, '**', yielded=True):
        print(('/'.join([p, sp]), sv))


[Bug]: drop index do not generate drop index ddl

ODC version
4.2.3
OB version
all
What happened?

What did you expect to happen?
generate drop index success
How can we reproduce it (as minimally and precisely as possible)?
drop index in table editor
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 38cb6946e7b726a4c34231a11e6190e5df20927e
------
咏和
Tue Dec 12 16:35:54 2023 +0800

pass


Build assets aren't included in the build output in production mode (regression from 5.1.0 to 5.1.1)

Bug report
What is the current behavior?
I have project which uses the mini-css-extract-plugin to extract the styles to a CSS file. However, the resulting css file seems to be marked as an orphan, and not included in the final build output during a production build. This is a regression from Webpack 5.1.0 to 5.1.1, in the former, the css file is present in the dist/ folder.
If the current behavior is a bug, please provide the steps to reproduce.
This is the same project setup as listed on https://webpack.js.org/plugins/mini-css-extract-plugin/
src/index.js:
import './style.css';

src/index.css:
body {
	background: green;
}

webpack.config.js:
const CssExtractPlugin = require('mini-css-extract-plugin');

module.exports = {
	plugins: [new CssExtractPlugin()],
	module: {
		rules: [
			{
				test: /\.css$/i,
				use: [CssExtractPlugin.loader, 'css-loader'],
			},
		],
	},
};

If I run Webpack with npx webpack --mode=production, no "main.css" file is present in the output folder.
If I run Webpack with npx webpack --mode=development, the file is properly created.
What is the expected behavior?
I expect the css file to be present in the output folder, so it's consistent with Webpack 5.1.0 and older.
Other relevant information:
Webpack version:  5.1.1
Node.js version: v14.13.1
NPM version: v6.14.8
Operating System: Ubuntu 20.04.1
Additional tools:

I've bisected it to this commit: https://github.com/webpack/webpack/commit/50c3a83340605694c90ff6973e3bd103763b88d9

Thanks for issue, keep using<EMAIL_ADDRESS>fix will be soon

Seems like this case slipped through the process. I think our test suite still runs against an older version of mini-css.
I revert the change until I find a better fix tomorrow.

@JessevanAssen can you test?

Thanks for the quick response! The issue is not present any more in 5.1.2.
Also, I've tested @sokra's assumption, and indeed the tests are running against an older version of mini-css. If I bump it to the latest version, the tests that cover the mini-css-extract-plugin indeed start to fail.

Could you try again with 5.1.3?

Yep, my use case works with 5.1.3 as well :). Thanks for the quick response!


Manager does not delete images not defined in the image YAML files

Running the Image-Manager I found that the it does not delete images not defined in the image YAML files as intended. Using the --hide setting, It does not only keep the last 3, but /all/ old images, way beyond the versions defined in our respective YAML files.
Expected Behavior: The Image Manager keeps the last 3 Images (Hidden) and deletes, deactivates, all other images tagged managed_by_x.

It would probably be good to have this functionality as a "Garbage Collection" flag with the manager command as there are some setups where deletion of an Image is impossible once there have been instances created from it. (COW)

Having a GC makes sense to me.

Should be fixed with #506.
When using multi=true, only the newest image is kept, while all older ones are hidden/deactivated/deleted.

Should be fixed with #506. When using multi=true, only the newest image is kept, while all older ones are hidden/deactivated/deleted.

that is what the manager does, but the expected behavior is still not enacted:
https://github.com/osism/openstack-image-manager/issues/568

There is now a warning message for images not longer defined. But they will not be deleted by default.


Dartium tests should respect VMOptions from test files

Certain tests require the correct options to be passed to the VM to pass. Dartium needs to pass these on to Dart VM when running Dartium tests.
One example is language/issue13474_test.

Because we use a pool of open Dartium browsers to run all the dartium tests, we don't have a separate browser instance for each test.  Therefore we can't pass separate dart VM options to dartium for each test.  Since Dartium is heading for deprecation, I don't think this is worth fixing.


Tweaks

Added objects like "productName", "description", "repository" and "bugs", and updated the dependencies.

I'm pretty sure that everything is ok, it's just I didn't know that I have to accept Babel version in travis-cli.


get nothing if there is @Data annotation on the entity class

Describe the bug

If an entity class has annotation @Data from lombok library, we get nothing from database.
It still not works when we put @NoArgsConstructor on the entity class.
If we remove all annotations from lombok library and generate all getter and setter, it works.

I'm not sure if it's an issue here or should we report it to spring r2dbc, just create an issue here for tracking.
To Reproduce
db schema:
create table user (
    id bigint auto_increment primary key ,
    name varchar(20) not null ,
    age tinyint not null
) engine = InnoDB;

entity class:
import lombok.Data;
import org.springframework.data.annotation.Id;
import org.springframework.data.relational.core.mapping.Table;

@Data
@Table("user")
public class User {
    @Id
    private Long id;
    private String name;
    private Integer age;
}

Hello, @victor-yi.
Thank you for reaching out and providing the details of the issue you are encountering.
While I understand your concerns, it would be more appropriate to report this issue to the Spring Data Relational team, as it does not seem to be directly related to the r2dbc-mysql project.
Please feel free to reach out if you have any other questions or concerns related to the r2dbc-mysql project.
Thanks!


update for v1.0.0 release

Trying from my account given the permissions issues experienced by @theavey

"re-doing because somehow the repo admin did not have write permissions to my branch (even though allow edits from maintainers was checked)"

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

A simple typo fix PR is giving a token error there:
https://github.com/conda-forge/webservices-dispatch-action/pull/16

That error is from trying to make a pr from a fork and it rightly not having access to conda-forge secrets. It is unrelated to the error here.
Make sure the account you forked to is not an org and check the permissions checkbox.

I'm using my user-account, the box is/was checked.

It's probably a GitHub issue then. I've seen this before and it resolved itself.

You can rerender locally.


Edit: Televen

Channel ID (required)
Televen.ve
Channel Name
No response
Alternative Names
No response
Network
No response
Owners
No response
Country
No response
Subdivision
No response
City
No response
Broadcast Area
No response
Languages
No response
Categories
entertainment
NSFW
None
Launched
No response
Closed
No response
Replaced By
No response
Website
No response
Logo
No response
Notes
No response

@Carlinhos027 OK then put as it is.


Changing panel url to /

I'm going to develop small CRUD app based on the Laravel Panel, so I want to change routing from /panel/* to /*. It is really? Does Panel have some configuration for it?

@mrnull if you only need the crud , take look at rapyd.com , if you need other thing of panel too , you can send a pull request witch code change in route to load panel url from config files so anybody can just change it


Add release report

We already have a validations report, so the next step is a release report

Closed with #49


MLCP Export - Document Selector Issue

While exporting when I was using -document_selector  with date range conditions >= and <= ,I am not able to export the data
Sample XML
<root><loadTime>2017-05-03T02:08:00.796029-05:00</loadTime><name>John</name></root>
<root><loadTime>2017-05-03T07:08:00.796029-05:00</loadTime><name>Ram</name></root>
<root><loadTime>2017-05-05T07:08:00.796029-05:00</loadTime><name>Sam</name></root>

Consider the above XML are in the marklogic
When I tried to export using -document_selector
with condition as
/root[loadTime >= xs:dateTime("2017-05-03T02:08:00.796029-05:00") and loadTime <= xs:dateTime("2017-05-04T07:08:00.796029-05:00")

then in the output I got Zero records, even though we have data for it.
But when I gave > and < it is working.
/root[loadTime > xs:dateTime("2017-05-03T03:08:00.796029-05:00") and loadTime < xs:dateTime("2017-05-04T08:08:00.796029-05:00")

So can you please suggest us what is the issue when we use >= and <=?

Not sure if this is a copy/paste issue, but you missed a square bracket ] at the end.
Your example works for me, I was able to export documents.
Maybe you want to try options file. the > used in bash might be a problem.

Please provide a reproducible test case, including the sample data, mlcp command and mlcp output log.

Please re-open when the requested information is provided.
Thanks.


Add gettext so envsubst is available

what/why

Add the gettext library so envsubst is available to use

/test


handling of super(arg) in #6e5064f seems wrong

In this example super(bar) gets turned into superbar and the bar argument was used.
[... bundle output ...]
Using rubocop 0.37.0 from git://github.com/bbatsov/rubocop.git (at master@6e5064f)
Bundle complete! 1 Gemfile dependency, 8 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
✔ ~/tmp
12:52 $ cat foo.rb
def self.foo(bar)
  super(bar) do
    puts 'in the block'
  end
end
✔ ~/tmp
12:52 $ bundle exec rubocop --auto-correct --config /dev/null foo.rb
Inspecting 1 file
W

Offenses:

foo.rb:1:14: W: [Corrected] Unused method argument - bar. If it's necessary, use _ or _bar as an argument name to indicate that it won't be used. You can also write as foo(*) if you want the method to accept any arguments but don't care about them.
def self.foo(bar)
             ^^^
foo.rb:2:8: C: [Corrected] Do not use parentheses for method calls with no arguments.
  super(bar) do
       ^

1 file inspected, 2 offenses detected, 2 offenses corrected
✔ ~/tmp
12:52 $ cat foo.rb
def self.foo(_bar)
  superbar do
    puts 'in the block'
  end
end
✔ ~/tmp
12:52 $ bundle exec rubocop -V
0.37.0 (using Parser <IP_ADDRESS>, running on ruby 2.3.0 x86_64-darwin15)

The same error persists even when bar is more "obviously" used with more verbose code e.g.:
class Base
  def self.foo(bar)
    puts "Base.foo called with #{bar.inspect}"
    yield if block_given?
  end
end

class InheritsFromBase < Base
  def self.foo(bar)
    super(bar.reverse) do
      puts 'in the block'
    end
  end
end

InheritsFromBase.foo('hgulp')
Base.foo('XYZZY')

There is a bugfix in my open PR which will likely fix this one too.

This is fixed on master. Let's close.


HTTP response status codes descriptions have dangling : in Check if a user is blocked by ...

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/rest/orgs/blocking#check-if-a-user-is-blocked-by-an-organization--status-codes
https://docs.github.com/en/rest/users/blocking#check-if-a-user-is-blocked-by-the-authenticated-user--status-codes
What part(s) of the article would you like to see updated?
Actual
Orgs

Status code
Description

204
If the user is blocked:

404
If the user is not blocked:

Users

Status code
Description

204
If the user is blocked:

304
Not modified

401
Requires authentication

403
Forbidden

404
If the user is not blocked:

Expected
Orgs

Status code
Description

204
If the user is blocked

404
If the user is not blocked

Users

Status code
Description

204
If the user is blocked

304
Not modified

401
Requires authentication

403
Forbidden

404
If the user is not blocked

(Probably, unless there's supposed to be text after the :)
Additional information
It'd be really nice if there was a see-also link between these two pages:
https://docs.github.com/en/rest/orgs/blocking
https://docs.github.com/en/rest/users/blocking

@jsoref
Thanks so much for opening an issue! I'll triage this for the team to review :eyes:


Bug: Threat Intel prevent one record to be normalized more than once

Background
A flag normalized_record_appened in rules engine prevent one record to be normalized more than once when threat intel feature is enabled.
Description

Requirement: threat intel is enabled.
Consider following rules,

        @rule(datatypes=['fileHash'], outputs=['s3:sample_bucket'])
        def match_file_hash(rec):
            """The rule to match file hash"""
            return 'streamalert:ioc' in rec and 'md5' in rec['streamalert:ioc']

        @rule(datatypes=['fileHash', 'sourceDomain'], outputs=['s3:sample_bucket'])
        def match_source_domain(rec):
            """The rule to match source domain and file hash"""
            return 'streamalert:ioc' in rec

With a record

{
    "Field1": {
	"SubField1": {
 	  "key1": 17,
	  "key2_md5": "md5-of-file",
          "key3_source_domain": "evil.com"
        },
        "SubField2": 1
    },
    "Field2": {
        "Authentication": {}
    },
    "Field3": {},
    "Field4": {}
}

This record will never match to 2nd rule match_source_domain, because the 1st rule triggers triggers to run data normalization against record and set the flag normalized_record_appened to True. So the record will be skipped to match other rules.

Desired Change

Allow one record to be normalized multiple times.

The fix in PR #655 causes memory exhausting issue and the PR has been reverted in #665. Reopen this issue.


Bosh v2 style manifest

Hi..
Is there Bosh v2 style manifest?

The README contains instructions using BOSH CLI v2. Manifests are located at the manifests directory.


I can't install Lunar with Laravel v11.35.0 (PHP v8.4.1)

I use Laravel v11.35.0 (PHP v8.4.1)
composer require lunarphp/lunar -W

./composer.json has been updated
Running composer update lunarphp/lunar --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires lunarphp/lunar * -> satisfiable by lunarphp/lunar[0.1.1, ..., 0.8.1].
- lunarphp/core[0.1.6, ..., 0.2.7] require laravel/framework ^8.0|^9.0 -> found laravel/framework[v8.0.0, ..., v8.83.29, v9.0.0, ..., v9.52.18] but it conflicts with your root composer.json require (^11.31).
- lunarphp/core[0.3.0, ..., 0.8.1] require laravel/framework ^9.0|^10.0 -> found laravel/framework[v9.0.0, ..., v9.52.18, v10.0.0, ..., v10.48.25] but it conflicts with your root composer.json require (^11.31).
- lunarphp/lunar[0.1.1, ..., 0.1.5] require lunarphp/licensing dev-main -> found lunarphp/licensing[dev-feature/laravel_10, 0.1, ..., 0.5.x-dev, 2.0-beta] but it does not match the constraint.
- lunarphp/lunar 0.1.6 requires lunarphp/core 0.1.6 -> satisfiable by lunarphp/core[0.1.6].
- lunarphp/lunar 0.2.0 requires lunarphp/core 0.2.0 -> satisfiable by lunarphp/core[0.2.0].
- lunarphp/lunar 0.2.1 requires lunarphp/core 0.2.1 -> satisfiable by lunarphp/core[0.2.1].
- lunarphp/lunar 0.2.2 requires lunarphp/core 0.2.2 -> satisfiable by lunarphp/core[0.2.2].
- lunarphp/lunar 0.2.3 requires lunarphp/core 0.2.3 -> satisfiable by lunarphp/core[0.2.3].
- lunarphp/lunar 0.2.4 requires lunarphp/core 0.2.4 -> satisfiable by lunarphp/core[0.2.4].
- lunarphp/lunar 0.2.5 requires lunarphp/core 0.2.5 -> satisfiable by lunarphp/core[0.2.5].
- lunarphp/lunar 0.2.6 requires lunarphp/core 0.2.6 -> satisfiable by lunarphp/core[0.2.6].
- lunarphp/lunar 0.2.7 requires lunarphp/core 0.2.7 -> satisfiable by lunarphp/core[0.2.7].
- lunarphp/lunar 0.3.0 requires lunarphp/core 0.3.0 -> satisfiable by lunarphp/core[0.3.0].
- lunarphp/lunar 0.3.1 requires lunarphp/core 0.3.1 -> satisfiable by lunarphp/core[0.3.1].
- lunarphp/lunar 0.3.2 requires lunarphp/core 0.3.2 -> satisfiable by lunarphp/core[0.3.2].
- lunarphp/lunar 0.4.0 requires lunarphp/core 0.4.0 -> satisfiable by lunarphp/core[0.4.0].
- lunarphp/lunar 0.4.1 requires lunarphp/core 0.4.1 -> satisfiable by lunarphp/core[0.4.1].
- lunarphp/lunar 0.4.2 requires lunarphp/core 0.4.2 -> satisfiable by lunarphp/core[0.4.2].
- lunarphp/lunar 0.5.0 requires lunarphp/core 0.5.0 -> satisfiable by lunarphp/core[0.5.0].
- lunarphp/lunar 0.5.1 requires lunarphp/core 0.5.1 -> satisfiable by lunarphp/core[0.5.1].
- lunarphp/lunar 0.5.2 requires lunarphp/core 0.5.2 -> satisfiable by lunarphp/core[0.5.2].
- lunarphp/lunar 0.5.3 requires lunarphp/core 0.5.3 -> satisfiable by lunarphp/core[0.5.3].
- lunarphp/lunar 0.5.4 requires lunarphp/core 0.5.4 -> satisfiable by lunarphp/core[0.5.4].
- lunarphp/lunar 0.5.5 requires lunarphp/core 0.5.5 -> satisfiable by lunarphp/core[0.5.5].
- lunarphp/lunar 0.5.6 requires lunarphp/core 0.5.6 -> satisfiable by lunarphp/core[0.5.6].
- lunarphp/lunar 0.6.0 requires lunarphp/core 0.6.0 -> satisfiable by lunarphp/core[0.6.0].
- lunarphp/lunar 0.6.1 requires lunarphp/core 0.6.1 -> satisfiable by lunarphp/core[0.6.1].
- lunarphp/lunar 0.6.2 requires lunarphp/core 0.6.2 -> satisfiable by lunarphp/core[0.6.2].
- lunarphp/lunar 0.6.3 requires lunarphp/core 0.6.3 -> satisfiable by lunarphp/core[0.6.3].
- lunarphp/lunar 0.6.4 requires lunarphp/core 0.6.4 -> satisfiable by lunarphp/core[0.6.4].
- lunarphp/lunar 0.7.0 requires lunarphp/core 0.7.0 -> satisfiable by lunarphp/core[0.7.0].
- lunarphp/lunar 0.7.1 requires lunarphp/core 0.7.1 -> satisfiable by lunarphp/core[0.7.1].
- lunarphp/lunar 0.7.2 requires lunarphp/core 0.7.2 -> satisfiable by lunarphp/core[0.7.2].
- lunarphp/lunar 0.7.3 requires lunarphp/core 0.7.3 -> satisfiable by lunarphp/core[0.7.3].
- lunarphp/lunar 0.7.4 requires lunarphp/core 0.7.4 -> satisfiable by lunarphp/core[0.7.4].
- lunarphp/lunar 0.7.5 requires lunarphp/core 0.7.5 -> satisfiable by lunarphp/core[0.7.5].
- lunarphp/lunar 0.7.6 requires lunarphp/core 0.7.6 -> satisfiable by lunarphp/core[0.7.6].
- lunarphp/lunar 0.8.0 requires lunarphp/core 0.8.0 -> satisfiable by lunarphp/core[0.8.0].
- lunarphp/lunar 0.8.1 requires lunarphp/core 0.8.1 -> satisfiable by lunarphp/core[0.8.1].
You can also try re-running composer require with an explicit version constraint, e.g. "composer require lunarphp/lunar:*" to figure out if any version is installable, or "composer require lunarphp/lunar:^2.1" if you know which you need.

I try
composer require lunarphp/lunar:^2.1

./composer.json has been updated
Running composer update lunarphp/lunar
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires lunarphp/lunar ^2.1, found lunarphp/lunar[dev-main, dev-0.7_0.8_branch_merge, dev-1.0.0-alpha, dev-1.0.0-beta, 0.1.0-rc.1, ..., 0.x-dev, 1.0.0-alpha.1, ..., 1.x-dev] but it does not match the constraint.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Originally posted by @tarikkamat in https://github.com/lunarphp/lunar/discussions/2036

@tarikkamat try this, Laravel 11 support is in the beta versions.
composer require lunarphp/lunar:"^1.0.0-beta" -W
Happily installed for me with these in composer.json
"laravel/framework": "^11.9",
"lunarphp/lunar": "^1.0",

Hi @tarikkamat
Change minimum stability to dev is mandatory while is not a release version ready
https://docs.lunarphp.io/core/installation.html#composer-require-package
composer config minimum-stability dev


Unable to do a MSET and MGET using batch

I'm trying to do a MSET and MGET on cluster configuration, but seems like the keys are not getting set when done through BATCH

@nethramadesh seems like it's not supported


CastleDB level editor support

I haven't tested this with this plugin at all, but CastleDB has a built in level-editor that may be useful for some people. If someone wants to take this on, be my guest!

it may be useful for me , could i test it?

I've done zero work on trying to get the level editor working with this. Happy to accept PRs that implement it though and along with a list of their decisions/how their implementation was chosen.


POST request not working

Your script working on GET parameter. But what about the POST request?

Hey S0ykot thanks for asking
So

Is important to mention that jeeves takes url, he cant read requests like this
About the post method support, im working on it

Waiting for the POST request script.


Support starting streams on Delta tables from a given version or timestamp

Support streaming source options startingVersion or startingTimestamp to start processing a stream (in its first micro-batch) from a given version onwards. In this mode, we should not create a Snapshot at that version, but start tailing the transaction log at that version onwards. If a checkpoint is available, we should continue from the state that is in the checkpoint.

I got it.

Will we expect this next release?

Will we expect this next release?

I'm not sure what their release cycle is. It may not be in 0.8.0 depending on how soon it is cut.


Configure connection details for azurerm_mysql_server

Configured the same way was the postgres server resource

/test-examples="examples/dbformysql/server.yaml"

Currently, we have a manual-intervention annotation on the dbformysql.Server resource's example manifest. Planning to open a follow-up PR to remove this annotation so that we can also validate the resource via uptest.


Placeholder not showing....?

I just recently started using this library and I can't set a placeholder....
<PhoneInput
            style={styles.textInput}
            flagStyle={{ marginHorizontal:10 }}
            allowZeroAfterCountryCode={false}
            textStyle={{ letterSpacing:1 }}
            ref={input}
            initialCountry={'us'}
            textProps={{ placeholder:'Please Enter Phone Number' }}
            translation="eng"
          />

This is my code and it doesn't set placeHolder. Is there any fix for this???

i have the same error, Someone fix it ?

I just recently started using this library and I can't set a placeholder....
<PhoneInput
            style={styles.textInput}
            flagStyle={{ marginHorizontal:10 }}
            allowZeroAfterCountryCode={false}
            textStyle={{ letterSpacing:1 }}
            ref={input}
            initialCountry={'us'}
            textProps={{ placeholder:'Please Enter Phone Number' }}
            translation="eng"
          />

This is my code and it doesn't set placeHolder. Is there any fix for this???

You have to add this line of code
<PhoneInput
style={styles.textInput}
flagStyle={{ marginHorizontal:10 }}
allowZeroAfterCountryCode={false}
textStyle={{ letterSpacing:1 }}
ref={input}
initialCountry={'us'}
textProps={{ placeholder:'Please Enter Phone Number' }}
translation="eng"
textInputProps={{ placeholderTextColor: Common.greyColor.color }}
/>

Please make a PR and I will review.
On Tue, Aug 16, 2022, 1:09 PM Diego Ruiz Torres @.***>
wrote:

i have the same error, Someone fix it ?
—
Reply to this email directly, view it on GitHub
https://github.com/rili-live/react-native-phone-input/issues/31#issuecomment-1216979722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXGCEVAYIAEUZ5C3EVNMFDVZPKLZANCNFSM5PNSFTRA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


tool http

hi, how to setup a tool that just performs a http request? similar to the ones in open ai gpts, that would be an awesome way to extend it

i can implement that tool if it doesn't exists, who is keeping track of the road map here?

Bump. Surprised to see there's no openapi tools


How to work when Android app closed

Many, including myself, have problems getting the android notifications to work while the app is asleep (active or background works great).  Since this seems to be very common complaint, can you first tell me what i might need to do to get it to work while app is asleep.  And second.. could you possibly devote a title and section on this page to this subject.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 92f390d9-cbd0-ab8c-6c8c-49df76d1b8e0
Version Independent ID: 15739c2f-afbb-c21d-b96f-fabe7060e410
Content: Send and receive push notifications with Azure Notification Hubs and Xamarin.Forms - Xamarin
Content Source: docs/xamarin-forms/data-cloud/azure-services/azure-notification-hub.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @profexorgeek
Microsoft Alias: jusjohns

One thing i'm thinking as i look around for help... is that i just noticed that i need to be using AndroidX.. i guess i missed that wave.. and just now realized it... so i swapped out all my Nugets to AndroidX nugets instead of Android.Support.****  nuget packages.  I'm thinking that is a main reason why for everyone else this 'just works' and mine has issues when app is closed.
So i'm not positive that is a fix it would seem like a good idea.
i put it as target framework 10 instead of target framework 9.  And Xamarin Forms versino is 4.8.xxxx
However i'm getting this one error, and cant find what Nuget Packages is still referencing   Xamarin.Support..******
Assembly 'Xamarin.Android.Support.v4' is using '[assembly: Java.Interop.JavaLibraryReferenceAttribute]', which is no longer supported. Use a newer version of this NuGet package or notify the library author
If this works then maybe add it to the documentation ( need  to be using Xamarin.AndroidX nugets over Xamarin.Support   + Xamarin.Forms version 4.5 or greater, and Android Target Framework 10+).  Again not sure if this is the case but i would think it would make sense why it's not 'just working' when app is closed - after following documentation when it works for others.

Hi @HUBBER12
It makes sense that AndroidX is now required. The requirements on Google Play is that new apps must target AndroidX (or higher), and from last week app updates also have to target AndroidX or higher (see https://developer.android.com/distribute/best-practices/develop/target-sdk). Because of that, any bug fixes to Xamarin libraries will only be made in AndroidX packages. In addition, Xamarin.Forms 5.0 (the next release) requires the use of AndroidX.
Re: the Xamarin support library that's still being found. If the package isn't directly installed in your project, it'll be the case that a package in your project has a dependency on Xamarin.Android.Support.v4. So you either need to eliminate that dependency, or perhaps you could try relying on AndroidX migration instead.
I'll get something added to the doc about requiring AndroidX.

I've updated the doc in a PR that will go live later this week.


Middle-clicking hash links may not jump

Describe the bug
Middle-clicking hash links on https://kit.svelte.dev/ may sometimes not jump to the hash.
Reproduction
Go to kit.svelte.dev/docs/errors. Middle-click on the first two hash links, "Error" and "type safety".
The "Error" link will, but the "type safety" link will not jump to the hash in the new tab, in these browsers:

Chrome 114.0.5735.133
Chromium 114.0.5735.133

(tested with fresh installs)
It will jump in these browsers:

Firefox 114.0.2 (fresh install)
Ungoogled Chromium 114.0.5735.106 (though I am not 100% sure if it did all the time, see below).

Interesting: developer.mozilla.org/.../Object/defineProperty also shows the same behavior in Chrome and Chromium 114.0.5735.133, and also in Ungoogled Chromium 114.0.5735.106 (weird), but it works in Firefox 114.0.2.
So, this may be a bug recently (re?)introduced in Chrome?
#4216 may be related. I can confirm that the link posted there does only scroll to the hash in Firefox. Middle clicking it in Chrome, Chromium and Ungoogled Chromium does not scroll to the hash.
For the records, the following document works in all browsers, middle-clicking the hash link jumps to the hash in the new tab:
<!DOCTYPE html><title>Jump to hash test</title>

Jump to #hash

#hash

Logs
No response
System Info
System:
    OS: Linux 5.15 Linux Mint 21.1 (Vera)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
    Memory: 12.10 GB / 15.36 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.3.1 - ~/Node.js/v20.3.1/bin/node
    Yarn: 1.22.19 - ~/Node.js/v20.3.1/bin/yarn
    npm: 9.7.2 - ~/Node.js/v20.3.1/bin/npm

Severity
annoyance
Additional Information
My guess is, SvelteKit tries to jump to something which is not yet rendered?

Also does not work in this version of Chrome and Chromium:
114.0.5735.198

This goes back to a bug within Svelte itself, where certain @html tags are not hydrated correctly, which means they get removed and reappended to the dom. Chrome doesn't find the id (race condition probably) and therefore doesn't scroll.

BTW, I just tested this locally and there, both links scroll to the correct position in all browsers. It just does not work over the internet.

Why are you closing it? I still see the bug on the current website. The issue persists.


Better, more future proof Fiona and Shapely usage

Hi, Sean Gillies here, the author of Fiona and Shapely. I'm very pleased to see them being used in your project! Shapely is a spin off of the Pleiades Project, a gazetteer of the ancient world. Gazetteers helping gazetteers :)
This pull request will future proof your ETL scripts. The shapely.geometry.asShape() and fiona.collection() methods aren't for developers. I've replaced them with calls to shapely.geometry.shape() and fiona.open(), documented methods of the public APIs of those packages.

@timwaters should I make a new pull request at https://github.com/topomancy/gazetteer? Is this one ever going to get acted on here? And how are changes at the topomancy repo going to get back to this one?

yes, feel free to make the pull request to the topomancy repository, thanks!


add ability to add spec to Deployment after object creation

Description of the feature or enhancement:

After creating a k8s.Deployment it seems not possible to add a k8s.DeploymentSpec.
Use Case:

Making code easier to read and more flexible.
"You can express rich interactions with methods and properties" from programmatically defined Helm chart.
Proposed Solution:

>>> d = k8s.Deployment(c, 'deployment')
>>> d.spec = k8s.DeploymentSpec(...)

This is a :rocket: Feature Request

Duplicate #160


Null bug fix

This one liner should resolve the "null" bug on the first thread response from a staff member leaving the message uneditable.

Thank you for the PR! And sorry for the delayed merge.


chore: simplify uploaded published data

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR updates contract publishing logic by adding compilers to metadata and improving version validation.
Detailed summary

Added compilers field to contract metadata
Improved version validation in publishContract function
Updated imports in publish.ts
Added new functions for contract publishing in tests

The following files were skipped due to too many changes: packages/thirdweb/src/extensions/thirdweb/write/publish.test.ts

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4611  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joaquim-verges and the rest of your teammates on  Graphite


Update licensing-governance.md

I have been discussing with Steve Conn (SR PRODT MARKETING MGR - Identity) and Marcelo di Iorio (Identity GBB) because of some doubts of customers in Western Europe that doing a bad interpretation of the examples will be under-licensing. The clarification I added in the lifecycle workflows example will help us to have those discussions around proper number of licenses. Please reach out to Steve<EMAIL_ADDRESS>), Marcelo (
<EMAIL_ADDRESS>) and myself (
<EMAIL_ADDRESS>) via teams for any doubt you may have. Thank you very much.

#sign-off

#hold-off

This was handled in a new PR.
#please-close.


x/website: SHA256 Checksum incorrect in Ubuntu

What version of Go are you using (go version)?

trying to download go1.15.5.linux-amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
Ubuntu, 64 bit

What did you do?
Download the file with command curl -O [file url]
What did you expect to see?
Same checksum as on the site: 9a58494e8da722c3aef248c9227b0e9c528c7318309827780f16220998180a0d
What did you see instead?
:~$ sha256sum go1.15.5.linux-amd64.tar.gz
2a862fbe29f35d8d24d68c8cf3f60c7cb0c3ac80a7875b8651e23c2fb5cb3d13  go1.15.5.linux-amd64.tar.gz

Thanks for reporting, we'll take a look.
CC @golang/release.

you need to follow redirects, the contents of your download is:
Found.

I've downloaded Go fromhttps://golang.org/dl/go1.15.5.linux-amd64.tar.gz and have been unable to reproduce your results.
shasum -a 256 ./go1.15.5.linux-amd64.tar.gz
9a58494e8da722c3aef248c9227b0e9c528c7318309827780f16220998180a0d  ./go1.15.5.linux-amd64.tar.gz

sha256sum ./go1.15.5.linux-amd64.tar.gz
9a58494e8da722c3aef248c9227b0e9c528c7318309827780f16220998180a0d  ./go1.15.5.linux-amd64.tar.gz

Where did you retrieve your file from?

I was able to reproduce your findings with @seankhliao comment. I'm going to close this issue since it is not an issue with the Go project. Please feel free to open it again if you believe otherwise.

Yep, you were right @seankhliao !  Thanks for the quick replies!!


Symfony 3 support

This bundle doesn't support Symfony 3 yet, and I don't have the time to work on this myself.
The FOSUserBundle already supports Symfony 3 so a majority of it's logic can be reused to make this bundle compatible.
If anyone is willing to fix this please open a pr. And if you are interested in helping with this project please contact me :+1: #96

Hi, I have been using this bundle in many of my project which were symfony2 projects. Right now I am working on making this bundle work with Symfony3.

@broncha Hi, Have you done working on making this bundle work with Symfony3?

@broncha Hi, Have you done making this bundle work with Symfony3?


dokku 1 click app not working

Installed server but when then go to the IP address of the droplet, it fails to connect.  Tried several times.

You haven't supplied much context, but for future readers experiencing something similar: I managed to solve it by deleting the 1-click droplet, and starting again with a clean droplet, then installing dokku.
At the time of this writing, Dokku 1-click comes with a very dated version of Dokku. There might be something deprecated going on. You could also try creating a 1-click droplet and immediately upgrading everything.


pywebpush update to 0.6.1

Description:
https://github.com/web-push-libs/pywebpush/releases/tag/0.6.1
Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

Did you test it locally?

@balloob yup


Remove phone model from User-Agent

Currently, the UA contains the phone model. E.g.:
Mozilla/5.0 (Linux; Android 8; SM-G930F) like AppleWebKit/...
It would be better if in the Privacy section there was an option to hide/remove the specific phone model from the user agent, like:
Mozilla/5.0 (Linux; Android 8) like AppleWebKit/...
And yes, this should be optional, I believe.

It's possible but not so nice, because it will not update the string after updating Kiwi and still show websites the old version. It would be great to just have this under privacy.

open kiwi://flags
search #reduce-user-agent
change flag to enabled
done

open kiwi://flags
search #reduce-user-agent
change flag to enabled
relaunch, done

 This one, right?

yes


inBackground option not available for ensureIndex

It seems that ArangoDB's inBackground option for ensureIndex (see: https://www.arangodb.com/docs/stable/indexing-index-basics.html#creating-indexes-in-background) is not available via arangojs.
Or, is it actually available and this is just a bug with the available typins for arangojs?

The parameter is undocumented for the HTTP API. I've asked for clarification whether this is an omission or intentional.

Interesting. I just assumed that arangosh was calling the HTTP API under the hood, so anything valid there was valid in the HTTP API.
Anyway, for reference, the other drivers do implement inBackground, so maybe the HTTP documents are out of date.

PHP: http://arangodb.github.io/arangodb-php/classes/ArangoDBClient.CollectionHandler.html#constant_OPTION_IN_BACKGROUND
Java: https://arangodb.github.io/arangodb-java-driver/latest/com/arangodb/model/IndexOptions.html#inBackground-java.lang.Boolean-
Go: https://github.com/arangodb/go-driver/blob/0817df9ff66e825e44f0731996f01c524df16f3c/collection_indexes.go#L94


Encoder/Decoder new Data Types support

[x] Unsigned VarInt
[ ] Double
[ ] UVarIntBytes (Compact Bytes)
[ ] UVarIntString (Compact String)
[ ] UVarIntArray (Compact Array)

Double is missing unit tests, the rest are missing implementation.
A solution to this #1048, still incomplete since I am unsure about these things:

should I stack the encoder.spec.js with more tests for each data type I implement?

in decoder.js the function readUVarInt() which was taken from the same place (stream-lib/Varint.java) the function writeUVarInt() was taken from.
The function throws an error if you try to decode a UVarInt with more than 5 bytes, is that fine to keep it throw statement there?
It also returns the value after unsigned right shift operation due to JavaScript's behavior with numbers. I explained it above the function but I am not sure if the explanation should stay there?
stream-lib does not  use VLQ they use LEB128 format, I am mentioning this since when I wrote the unit tests for the functions I instantly assumed VLQ was used and hit my head against the wall for a day wondering why the examples from the wiki give me different results so I added a comment above the function writeVarInt() stating that LEB128 is used.

Keeping naming convention encoder.js/decoder.js blind to Java.
Java & Kafka calls the last 3 data types in the list "Compact ???" due to the nature of LEB128 shrinking the request size in some situations, should the function names be for example writeCompactString() or writeUVarString()?

Some files like jsconfig.json and yarn.lock were added to this branch I am not sure what are the consequences of that but I assume that shouldn't happen.

Implementation isn't done and I am sure some of the things I listed are trivial but I would like to get a review for this 😊.
Edit 1:
I see that I did start implementing writeUVarIntArray(), naming question still remains.

should I stack the encoder.spec.js with more tests for each data type I implement?

Yes please. If it becomes unmanageably large we can start to split it apart.

The function throws an error if you try to decode a UVarInt with more than 5 bytes, is that fine to keep it throw statement there?

Yup. Just change it to throw a custom error instead of a generic Error.

It also returns the value after unsigned right shift operation due to JavaScript's behavior with numbers. I explained it above the function but I am not sure if the explanation should stay there?

I would prefer it if we can write a test that shows why it's necessary (i.e. it fails if we don't round the value to an int32) and has a descriptive name, but otherwise a comment is fine. The kind of code in Encoder is the kind where it's just about impossible to read and understand why certain things are done, so the more context we can preserve, the better.

Keeping naming convention encoder.js/decoder.js blind to Java.
Java & Kafka calls the last 3 data types in the list "Compact ???" due to the nature of LEB128 shrinking the request size in some situations, should the function names be for example writeCompactString() or writeUVarString()?

Good question! Given that we already have for example writeVarIntString I would stay consistent with that and make it writeUVarIntString.

I would prefer it if we can write a test that shows why it's necessary (i.e. it fails if we don't round the value to an int32) and has a descriptive name, but otherwise a comment is fine. The kind of code in Encoder is the kind where it's just about impossible to read and understand why certain things are done, so the more context we can preserve, the better.

I couldn't think of a test to showcase it's necessity. I believe a comment will save up some time for people who want to get to know the Encoder, the comment above writeVarInt() (that I edited a bit) stating where the code was originally taken from helped me a ton.
Regarding the new function I added writeUVarIntString() representing compact strings, as stated in the protocol guide "Represents a sequence of characters. First the length N + 1 is given as an UNSIGNED_VARINT . Then N bytes follow which are the UTF-8 encoding of the character sequence."
I don't know why Kafka decided to encode the length + 1, but I implemented the function with it:
this.writeUVarInt(byteLength + 1)

I couldn't think of a test to showcase it's necessity. I believe a comment will save up some time for people who want to get to know the Encoder,

Totally fine, and I agree. I was mostly talking about the general case. If we can explain something with a test, that's ideal, but when that's not doable or when it doesn't make it clear enough, a comment is great.

Thanks for the contribution!


[Deploy] Notion (With notifications)

Service
Notion (https://notion.so)
Link to your repository
https://github.com/AndrewLeedham/recipe-notion
Additional Information
I'm aware an issue has already been raised #99. But this version adds notifications and a filled in logo.

Hi @AndrewLeedham ! I'm the author of #99 I updated my repo with your improvements. I just didn't know that there are some problems with my recipe.


Installation problem on Archlinux

Hi,
Installation seems not working on Archlinux :

$ python2 setup.py install
running install
running build_ext
building 'gippy/libgip' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/GIP
gcc -pthread -fno-strict-aliasing -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fPIC -IGIP -I/usr/lib/python2.7/site-packages/numpy/core/include -I/usr/include -I/usr/include/python2.7 -c GIP/GeoVectorResource.cpp -o build/temp.linux-x86_64-2.7/GIP/GeoVectorResource.o -fPIC -O3 -std=c++11 -Wno-maybe-uninitialized
GIP/GeoVectorResource.cpp: Dans le constructeur ‘gip::GeoVectorResource::GeoVectorResource(std::__cxx11::string, std::__cxx11::string)’:
GIP/GeoVectorResource.cpp:37:30: erreur : ‘Open’ is not a member of ‘OGRSFDriverRegistrar’
_OGRDataSource.reset(OGRSFDriverRegistrar::Open(filename.c_str()), OGRDataSource::DestroyDataSource);
^~~~~~~~~~~~~~~~~~~~
GIP/GeoVectorResource.cpp:37:91: attention : ‘static void OGRDataSource::DestroyDataSource(OGRDataSource*)’ is deprecated [-Wdeprecated-declarations]
.reset(OGRSFDriverRegistrar::Open(filename.c_str()), OGRDataSource::DestroyDataSource);
^~~~~~~~~~~~~~~~~
In file included from GIP/gip/GeoVectorResource.h:28:0,
from GIP/GeoVectorResource.cpp:22:
/usr/include/ogrsf_frmts.h:245:25: note : declared here
static void         DestroyDataSource( OGRDataSource * ) OGR_DEPRECATED("Use GDALDataset class instead");
^~~~~~~~~~~~~~~~~
error: command 'gcc' failed with exit status 1

I tried with pip before :

$ pip install gippy
Collecting gippy
Using cached gippy-0.3.5.tar.gz
Building wheels for collected packages: gippy
Running setup.py bdist_wheel for gippy ... error
Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-_8sgx0ja/gippy/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" bdist_wheel -d /tmp/tmp6edpypnrpip-wheel- --python-tag cp35:
running bdist_wheel
running build_ext
building 'gippy/libgip' extension
creating build
creating build/temp.linux-x86_64-3.5
creating build/temp.linux-x86_64-3.5/GIP
gcc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fPIC -IGIP -I/usr/include/python3.5m -c GIP/tests.cpp -o build/temp.linux-x86_64-3.5/GIP/tests.o -std=c++11 -O3 -DBOOST_LOG_DYN_LINK
cc1plus: attention : command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from GIP/gip/GeoImage.h:25:0,
from GIP/gip/tests.h:25,
from GIP/tests.cpp:23:
GIP/gip/GeoResource.h:32:28: erreur fatale : gdal/gdal_priv.h : Aucun fichier ou dossier de ce type
#include <gdal/gdal_priv.h>
^
compilation terminée.
error: command 'gcc' failed with exit status 1

Failed building wheel for gippy
Running setup.py clean for gippy
Failed to build gippy
Installing collected packages: gippy
Running setup.py install for gippy ... error
Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-_8sgx0ja/gippy/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --record /tmp/pip-wq24jaxn-record/install-record.txt --single-version-externally-managed --compile:
running install
running build_ext
building 'gippy/libgip' extension
creating build
creating build/temp.linux-x86_64-3.5
creating build/temp.linux-x86_64-3.5/GIP
gcc -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fPIC -IGIP -I/usr/include/python3.5m -c GIP/tests.cpp -o build/temp.linux-x86_64-3.5/GIP/tests.o -std=c++11 -O3 -DBOOST_LOG_DYN_LINK
cc1plus: attention : command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from GIP/gip/GeoImage.h:25:0,
from GIP/gip/tests.h:25,
from GIP/tests.cpp:23:
GIP/gip/GeoResource.h:32:28: erreur fatale : gdal/gdal_priv.h : Aucun fichier ou dossier de ce type
#include <gdal/gdal_priv.h>
^
compilation terminée.
error: command 'gcc' failed with exit status 1
----------------------------------------

Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-_8sgx0ja/gippy/setup.py';exec(compile(getattr(tokenize, 'open', open)(file).read().replace('\r\n', '\n'), file, 'exec'))" install --record /tmp/pip-wq24jaxn-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-_8sgx0ja/gippy/

I have gdal_priv.h on my installation :

$ locate gdal_priv.h
/usr/include/gdal_priv.h
$ gdal-config --cflags
-I/usr/include

Any suggestion ?
Sincerely,
Sylvain

Hello Sylvain,
In the first case it looks like there might be a versioning issue of GDAL/OGR.   Can you check the gdal version?
$ gdalinfo --version
In the second case, with pip install, you are installing an older version (0.3.5) of GIPPY which has more dependencies, and is looking for the gdal header files in an include gdal/ directory (rather than just in include).
You can try
$ pip install gippy --pre
which will install the 1.0.0 beta version (pre allows installation of beta versions) rather than 0.3.5, but I suspect you may run into the same error as your first case.

Hi,
Thank you for the reply.
$  gdalinfo --version
GDAL 2.0.2, released 2016/01/26
Same error as the first related. Which version of gdal is required?

GDAL 2 is not yet supported, there's some underlying changes in OGR's handling of vector files.   It should work with any GDAL later than 1.9, I recommend 1.11, which is the version supplied on Ubuntu.

Ok thank you

@kikislater Please let me know if you were able to resolve this. If I don't hear back the issue will be closed this week.

No not solve. I stay in gdal 2 since it was release last year.
May be I have to fork gippy to adapt to gdal/ogr 2 but don't have any time at this moment ...

Thanks for the response @kikislater I am closing this out and will start a new issue for working with GDAL2.


Allow OpenId authentication and also refresh the tokens

Note: Would be good to merge it after https://github.com/abiquo/api-java-client/pull/33, since TokenRefreshResponse duplicated classes could be removed and api-transport-model version updated to 3.8.6

opening new pull to master


Update Gradle-License-Report to v2.8

For some reason Renovate hasn't been detecting updates to the license report
generator; upgrade to the latest version.

I see Renovate is just waiting for this release to be out for long enough before posting a PR; closing this.


Extension Commands Not Working - Command Not Found

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
Version: 1.67.2
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:20:04.972Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.5.0

OS Version: MacOS Monteray 12.4

Steps to Reproduce:
VSCode extension commands not working. For example "Project Manager" extension has a shortcut CMD+ALT+P to open project list to select. When I do that I get "command 'projectManager.listProjectsNewWindow' not found".
Doing it by using CMD+SHIFT+P to open the command palette and searching for the extension specific command also gives the same error
This is hapenning for all extensions. YAML+JSON extension produces this error "Command 'YAML+JSON: Preview as JSON (from YAML. Opens in new file)' resulted in an error (command 'extension.previewAsJson' not found)"
Tried restarting VSCode and Mac without any luck.

@pdomala can you run command "Show running extensions" to see if these extensions are activated successfully?

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


Optimize _.range

Prevents an arguments deopt.
http://jsperf.com/range-optimization

Cool, I can dig it.


Prevent errors when unplugging drives while the scripts are running

Fixes: https://github.com/resin-io-modules/drivelist/issues/147
See: https://github.com/resin-io/etcher/issues/1126
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

IMHO this PR should be regarded as WIP until the Windows script also gets updated similarly (we should aim to keep consistent behaviour across all three platforms).

@lurch My bad! The Windows part is done!

I couldn't avoid the extra indentation in some parts of the Windows script, given that VBScript has nothing similar to the continue keyword to go straight to the next loop iteration. The alternative was to create global Boolean variables, so I guess a bit of indentation is better :)

I couldn't avoid the extra indentation in some parts of the Windows script,

That's fine, it's just a shame the diff displayed by github isn't more tolerant to changing indent-levels ;-)

@lurch Do I have the green sign to merge? :)


Update dependencies

Update Camel and other dependencies with the dependency script

Part of Assimbly 3.9.0


Set up download analytics

It'd be great to be able to see data like:

Total downloads including torrents

direct vs torrent
32bit vs 64bit
per platform

Average price paid per download (excluding 0 as an outlier)

per platform (a la humble bundle)
direct vs torrent

Google Analytics can be used for the tracking, but presumably you'd want the averages to be public.
ga('send', 'event', 'category', 'action', 'label', value); // value is a number and not in quotes.
// Send and Event are always the same.
// Category is the Download
// Action is how it was initiated. Homepage, and maybe in the future, email?
// Label of Download
// Price paid in pence.
ga('send', 'event', 'Freya Beta Download', 'Homepage', '32-bit Magnet', 0);
ga('send', 'event', 'Freya Beta Download', 'Homepage', '64-bit Direct', 2500);

TBH I don't care if they're public. I'm more interested in knowing how much effort we should put into 32bit support & what are sane values for the pay-what-you-want buttons. But also the cynic in me wants to know who's the cheapest and who kicks down ;p

If we're not concerned about public ones, then this can be done entirely in JavaScript with a load of ifs and Google Analytics.
ga('send', 'event', 'Freya Beta Download (Architecture)', 'Homepage', '32-bit', 0);
ga('send', 'event', 'Freya Beta Download (Method)', 'Homepage', 'Magnet', 0);
ga('send', 'event', 'Freya Beta Download (OS)', 'Homepage', 'Windows', 0);

Make it so, Number 1


Prisma Client: fixing type name clashes from generated client

Internal Slack 🧵
Internal Notion doc
During type generation, we create many different TS types based on a schema. Sometimes, generated type clashes with some other model type or internal helper type we are using. In that case, generated client usually becomes unusable.
List of open issues with type-clash) topic label

Introduce $Model namespace for user-defined models, enums and composites
Introduce sub-namespaces for generated types
Move all helpers into the runtime module

Notes

No changes required from the users for the most part. For the types that might actually be used on their projects, we keep an alias with a short name as an export if it does not conflict with other models. We remove it if it has a conflict, but that’s already broken. So, I don’t think it is possible to get from working project to non-working one with this change.
We should at least mention that Prisma.SomeModelArgs is now available as Prisma.$SomeModel.Args as well. If we decide that we want to recommend it (since it would never conflict with anything) we might specify that too and deprecate the old thing.
in order for it to work, we need to ensure that only fully-qualified names are used by the client itself.

All clashes except #15718 should be fixed in 5.1. That one can not be fixed in backward-compatible manner and have to wait until next major release.


Fix instanceof check and cast with pattern matching in webapps.

relates tp #85

@CBorowski-dev The PR contains quite some commits for the small changeset. This is because you use the "merge" option with git. You should think about using "rebase" instead. This keeps the commits cleaner.
Not a problem yet, the commits are anyway squashed before merging to main.

@CBorowski-dev Please add also "relates to #85" to the commit message body and PR description.


Added separate check for version argument

Closes #275
Optimized output of Installomator.sh version to output plain version

Thank you!


Packagist

Currently this package is not registered on Packagist so it can't be installed easily (ofc I can still add a vcs repo in my composer.json).

Done.

Thanks. Just to be safe, I think you should add more maintainers to the package - same as for other amphp packages.


Delete channel API cannot delete DM or GM channels

If we try to delete a DM or GM channel, the Job fails with an error:
{"timestamp":"2024-12-20 13:24:59.053 Z","level":"debug","msg":"Unable to delete direct or group message channels","caller":"web/context.go:120","path":"/api/v4/channels/7hq7ckpfpt8w3cg38csg7cphhy","request_id":"5iwkfyhhdjg6zkc4x9pcprze5o","ip_addr":"","user_id":"","method":"DELETE","err_where":"localDeleteChannel","http_code":400,"error":"localDeleteChannel: Unable to delete direct or group message channels"}

We previously deleted channels using SQL directly: https://github.com/davidkrauser/mattermost-plugin-bulk-user-delete/blob/2ec59c7d8e57becdff388c59a817e1f937e2347c/server/deletion.go#L78
We should consider going back to the old method for DM and GM channels (or potentially for all channels).
This was reported by @BenCookie95

We don't need to delete these channels - skipping over them is fine.


[Pending] [ERC20] Add tests

resolve #15

https://github.com/ethereum/vyper/issues/1095

Use pytest. #43


Don't run cron workflows in forks

When creating a fork (due to new TUF root veryifing, among others) and not deleting it after, the cron-scheduled actions would run on the fork but break due to missing credentials (e.g.,
1, 2).
According to https://github.com/orgs/community/discussions/26684, inserting this if statement should prevent the job from running. Did not insert it in actions that are following the main one since if the first one does not run none of the others would (if I read the guide properly). Also, did not add the if statement to the other workflow files since those are not run on cron and should actually run on PRs or workflow dispatch. Only cron jobs are the ones that need to be disabled.
Closes #515
Signed-off-by: Mihai Maruseac<EMAIL_ADDRESS>Summary
I got a fork of this repository that I sync to head when there is a new round of TUF root signing and it seems now we have actions that are running on cron and asking for credentials. Since the fork does not have them, the action fails. This results in notifications being sent to the fork owner.
Release Note
NONE
Documentation
NONE

Should we do this for every GHA?


[JFXTabPane] Header Width

How to change width of the JFXTabPane header, like.. I don't want it to be 100% wide, but for example 80% or less.

@jfoenixadmin
I think he wants to extend original JFXTabPane(Skin), and with a reflection change the width of HeaderContainer. Or add something to the same pane to make some kind of a decorator.


New approach for job container file system aspects

This change reworks the way that the file system aspects function for job containers.
This is a pretty radical difference, and adds in some new Windows APIs to
accomplish the job.
The gist of things, is instead of mounting the wcifs volume containing the unioned
view of the containers layers on the host at a certain path, and then treating this
as the "C:" of the container, we now bind the files from this volume on top of the hosts C drive.
This might sound odd, but it's possible for two reasons.

There is a file system minifilter in Windows that allows you to bind a filesystem
namespace to another path, so you see whatever was at the first path at the second,
akin to a bind mount on Linux.
This filter allows you to create these bindings at a per silo level. So only
processes in that silo will see these bindings. The binding will appear to be a unique
file system layout in each.

Before this change, the containers were just comprised of regular job objects so
we need to first upgrade the job to a silo, and then we start employing these bindings.
This change (irrelevant to the filesystem aspects but just for testing to try out something
different) now joins a network compartment if available, so it should only have access to
a virtual adapter.

Add bindings for the Bind Filter from bindfltapi.dll
Define a silo flag to be able to upgrade the containers job object to a silo
Rework the pod sandbox container for job containers. Previously we faked out
the pod sandbox container, as an optimization. But if we launch a normal Windows
Server Container as the pod sandbox always, then we can take advantage of the
network compartment that will be created, so we don't always have to use the
hosts network.
Rework directory mounts for job containers to also make use of the Bind Filter.

Signed-off-by: Daniel Canter<EMAIL_ADDRESS>

Closing as we explore other avenues for this work potentially


Support for pipelining data in datatables

Hello,
Is there support for pipelining data as shown in https://datatables.net/examples/server_side/pipeline.html in this package?

Yes this is already supported but not yet documented :). See PR https://github.com/yajra/laravel-datatables/pull/938 for ref.


Set startup console

Startup console
Specify the startup console such as WSL, PowerShell or CMD.

Found the way to set startup console. A separate console is known as a profile.
It can be set by using the defaultProfile: "guid" property...


Fix might_contain validate fallback

@zhejiangxiaomai Can you help review this one? I have tested locally

No, it fallback to vanilla before, now we can offload to gluten in gluten-it TPCH Q7 and Q8, I will test CI in https://github.com/oap-project/gluten/pull/1037


Add setup.py to allow atomate2 to act as a namespace package

This moves the atomate2 directory to the root of the package directory

I prefer a flat layout over a src layout as well. I moved everything into src to match the atomate2 structure and there are some benefits to the src layout (ref). We should be able to configure it to reference modules, for example, as from atomate2.openmm ... instead of from src.atomate2.openmm .... What's your reasoning for having the flat layout?

It was just the first thing I could get working with the namespace package setup in setup.py. I'm happy to go with a src layout if that works with the namespace packaging!

Ok I seem to have figured out how to make the src layout work with a namespace package. This now just adds a setup.py file and modifies all the imports.

I'm trying to understand if we need a setup.py and a pyproject.toml. The owner accepted answer in this SO post suggest that we can get away only having a toml file.

The fact this is a namespace package makes things trickier because we need to use setuptools, which until recently didn't have support for namespace packages.
It looks like that is now in Beta, so I can give it a try.

The fact this is a namespace package makes things trickier because we need to use setuptools, which until recently didn't have support for namespace packages.
It looks like that is now in Beta, so I can give it a try.
Maybe we merge for now and remove setup.py later? Currently I am running into all sorts of issues with the import src.* syntax. Have you been able to make it work on another system?

Sounds good! I haven't tested on any other platform than my mac. Happy to approve now and we can make an issue to re-visit removing setup.py and only maintaining a pyproject.toml.


Pull request to add RateMyProfessors data

Please check my request and maybe tell me what parts you want to keep or formatting needs to be done.
It currently scrapes RateMyProfessor for professor rating, comments, and the link to the site.

Sorry about the late response; closing this because I've responded now.


Mirror os.environ by allowing Env to be accessed like a dictionary

Would involve:

mapping a Env.__getitem__ function that maps to Env.__call__
a Env.__dict__ that outputs schema values
a Env.__str__ prints out dict

@LynnCo Thanks for the suggestion here! I'm somewhat hesitant to add this feature since it'll introduce another parallel API for interacting with envparse, one using __call__ and the other __getitem__. At least in a minor version upgrade.
Perhaps this suggestion could be implemented in an envparse 1.0 release.
If the schema was required to be defined up-front (which it currently isn't), then the limitation of the dictionary-API would be nearly as bad, and we could probably make it work.

Another option would be to provide a get() method that could work like:
foo = env.get('FOO', False)

With False being the default if it doesn't exist. This is honestly something I expected in the library and was sort of surprised when I didn't find it.

I'm closing a bunch of my older github issues ♻  feel free to open a new issue describing this same change! Or re-open this one, if someone is still interested in working on it 📝


Read final iteration count from GRASP ouput

Ideally we would also read the maximum number of iterations from the YAML file as well as the GRASP output. Both would be stored in the graspRun rslts dictionary.

This enhancement has been added, but need to push the changes. However, the changes are in CAMP2Ex branch. I will update this with commit hash for future reference.

The changes has been pushed to test branch with the commit hash 8bfad51


Feature: Manage Rank Only

Describe the feature
Possible permission for people to be able to manage officer rank only. What I mean by that is change an officers rank. Right now it seems to be tied to Manage Unit which means they can also do so many other things.
To be clear. I don't mean Manage Value Officer Rank. I mean Manage Unit Rank.
I don't want these people to be able to create ranks or edit ranks on the CAD as a whole.
I only want them to be able to change someone's rank when someone gets promoted or demoted.
Additional Context
Recently, that causes a security issue. If someone decides they want to mess with peoples officers they can easily do that. We only want to add the rank editing feature to some people so they cannot edit peoples officers any deeper than that.

In most cases, anybody in a position of power to manage a unit's rank, would also be able to manage the reset of the fields found on the Manage Units page. Is this incorrect?

In most cases, anybody in a position of power to manage a unit's rank, would also be able to manage the reset of the fields found on the Manage Units page. Is this incorrect?

This unfortunately leaves security issues. Editing their Callsigns/Name etc. Some trolls can easily (and have) gone in and changed peoples Officer or Callsign unit names.

Interesting. I will take a look this evening and see what might be possible!

Interesting. I will take a look this evening and see what might be possible!

any luck

Apologies for not replying, I thought I had lol. I've found a few possible implementations that could work, however I haven't had any time to test any out. Unfortunately my day-to-day is still quite busy, so I'm not sure I can give a time estimate for when this will be looked into.

On this topic I also noticed that LEO Supervisor is missing some options for permissions. At the moment they cannot change anyones callsign for example. It doesnt let us put that option even in for them. Unless we make them admin.


set ci runs on master and enable integration test on android alarm manager

Set up ci runs only on master
Make android alarm manager runs integration test with null safety

Should we land this? (With the android alarm changes?)

Yes, sorry; my approval was meant to come with an LGTM comment.