Unreal Engine 4.15+ Nativize Error

When you try to package the game as shipping and with Nativize as Inclusive the compiler find a problem with the Object Discord
"...Source/NativizedAssets/Public/BP_GameInstanceCore__pf2323974764.h(58) : Error: Unrecognized type 'UDiscordRpc' - type must be a UCLASS, USTRUCT or UENUM"
My Discord var there is a DiscordRPC Reference type, any idea or why this happen ?
*Visual Studio and all compiles fine, just happen at package and Nativize

I can take a look at this. It looks like it's marked as a UCLASS in the code, which is odd:
https://github.com/discordapp/discord-rpc/blob/f5f2d69a72954647a9c9e457324908b205502c4a/examples/unrealstatus/Plugins/discordrpc/Source/DiscordRpc/Public/DiscordRpcBlueprint.h#L82

So, I believe I've done the same steps that you have trying the sample application, and I could not repro. Are these settings correct?

Could you post part of the nativized code that errors?

Yeah like you have done, then make sure you have a GameInstance or some class and add a var called as you want based in the UObject of Discord

I'm using the version 4.15 but didn't tested the newer ones right now*

Where's your constructor?

I have no constructor, just the var, probably that is the problem ? Let me check :thinking:

Most likely.

Added the constructor

Solves nothing, I want to say without the constructor and without nativize the Discord system worked so...

The Outer must be a playercontroller AFAIK

Don't think so as have parts of other code I can't show, still looks total like a bug with UE4 or something ?
In other hand I can't create that using a player controller because must cross between levels and menus and basically as is in the GameInstance

When you nativize, the nativized code shows in intermediate "\Intermediate\Plugins\NativizedAssets". Open up the file it says its erroring at and pastebin it or something.

"UPROPERTY(EditDefaultsOnly, BlueprintReadWrite, meta=(DisplayName="Discord RPC", Category="Social", OverrideNativeName="DiscordRPC"))
UDiscordRpc* bpv__DiscordRPC__pf;"

The return error is the one I postd on top and the code is this one on the line 58

Can you post both the full .h and .cpp file of it instead?

As said no cause have included other libs and private content.
But I notice by adding in my project cs:
	PublicDependencyModuleNames.AddRange(new string[] { ... "DiscordRpc" ... });
	PublicIncludePaths.AddRange(new string[] {"DiscordRpc/Public" });

Fixes that problem but return me a different one with the Gameinstance trying to get something public

Glad you were able to get the help you needed here. Thank you Mootjuh for your assistance.


Jadeite and misleading non-unicode ought to have warning

This is the inverse of issue #460.
I pasted in the method text from the example (actually simplified into '-ß-ñ-α-€-∏-') into a Jadeite browser, and it pasted in fine, and compiled without complaint. However, the three unicode characters are messed with; the alpha is a, the euro looks normal but is 128/16r80, and the pi is ?.
There should be some kind of warning when you attempt to use characters that are going to be problems.
details:
I hand-edited methodOne in the tonel source, to have desired text, using vi on linux.
This loaded fine and produced pink warning as doc'd in #460.
In Jadeite browser, pasted text (copied from linux) into methodTwo.  It works perfectly and produces no errors (although if you look you can see that it's wrong),
In Jadeite, did a write to disk for the project.
The source is now.
{ #category : 'Test' }
Transient >> methodOne [
^'-ß-ñ-α-€-∏-'
]
{ #category : 'Test' }
Transient >> methodTwo [
^'-ß-ñ-a-<80>-?-'
]

It doesn't have a warning, exactly, in v3.2.12, but it's definitely not looking like it could be correct.
methodOne
^'-ÿŸ-ÿ±-ÿ±-â⿿¬-â˿-'
so closing this against retest and other fixes.


[BUG]: Template for D1 doesn't work as intended

What version of drizzle-orm are you using?
0.28.6
What version of drizzle-kit are you using?
0.19.13
Describe the Bug

Run the  "generate" command from drizzle-orm/examples/cloudflare-d1.
error: unknown option '--schema=src/schema.ts'

Expected behavior
Should run the up command as intended for D1
Environment & setup
Any environment as its probably a plain mistake.

I can merge myself if the proposed fix is okay:

Add drizzle.config.json with:

{
  "out": "drizzle",
  "schema": "src/schema.ts"
}

remove  --schema=src/schema.ts from package.json


Scheme reference file not found:

when i run this code: (artic minion --normalise 200 --threads 4 --scheme-directory ~/artic-ncov2019/primer_schemes --read-file run_name_barcode03.fastq --fast5-directory path_to_fast5 --sequencing-summary path_to_sequencing_summary.txt nCoV-2019/V3 samplename):
I get this error: (Scheme reference file not found: /Users/aroobalhumaidy/artic-ncov2019/nCoV-2019/V3/nCoV-2019.reference.fasta)

Sorry for the slow reply @AroobAlhumaidy - did you manage to get this working?
If not, let me know the output of:
ls -R ~/artic-ncov2019/primer_schemes


Scanning stop when it was Kokomi

Scanning stopped when it was Kokomi's turn in the character.

Yep same here. Tried putting koko in slots 8-4-1 and whenever it reaches kokomi > attributes the cursor stops for a minute or so, and then goes back to paimon menu and starts scanning other items ( that is, it skips all characters after Kokomi even if she's the very first character to be scanned. )

Hi there, this issue is hopefully resolved in the v1.1.1 prerelease. If it has been, please let us know so we can close this issue.


modified selector to the correct label

Hello,
same as #6, but for zabbix-server and zabbix-agent services.
Best regards,

Thank you! 👍


refactor: use slug as article URL route instead of the filename

In order to solve the problem that GridSome cannot encode Chinese as URLs (gridsome issue#956), the markdown files in the content are named in English currently, which makes the files not intuitive. Adding the slug property as the routing path can free file naming from the English language.

Mark: I also pull request #1513 to resolve build error when using the CJK characters as the post title while the title is a part of the URL route.


Migrate prior spendable outputs to OutputSweeper

From https://github.com/lightningdevkit/ldk-sample/pull/133#discussion_r1597596831.
Based on #133.

Rebased @tnull


metrics.csv always says cell count is -1

Description
cell count is reported as -1
Expected behavior
the true cell count
Environment
Kernel: Linux v5.15.0-50-generic
Distribution: ubuntu 20.04
Python: v3.8.10 (OK)
Container Engine: docker v20.10.7 (OK)
OpenLane Git Version: f9b5781f5ef0bbdf39ab1c2bbd78be8db11b27f2
pip: INSTALLED
pip:venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

f9b5781 2022-07-01T16:04:31+02:00 Fix a bug with `-overwrite` (#1171) - Anton Blanchard -  (grafted, HEAD, tag: 2022.07.02_01.38.08)

Reproduction Material
Run the flow with the spm example. Check the metrics, you will see cell_count is -1

And the other cell counts are most often wrong as well. For example DFF count is usually 0, even with hundreds of df type flops in a design.


Adds ability to specify input codec as a manifest property.

Signed-off-by: Derwei Chan<EMAIL_ADDRESS>This allows us to enable the multiline codec.

Hi - thanks for the PR! I have a question about your use case, if you don't mind. First some background and our understanding. We've experimented with multiline before (although with the filter, not the codec), but moved it out of the release and our manifest configuration because we felt it didn't scale on the deployment side of things.
In most cases, log parsers are one of the first bottlenecks in the deployment and it gets scaled by adding another job/vm. Once more than one log parser is running, ingested messages will very likely and unpredictably be split across the multiple log parsers without respect to their multiline nature. For example, messages A1 A2 B1 B2 C1 D1 are waiting in the queue - log_parser/0 receives a batch, A1 A1 B1, and log_parser/1 receives a batch, B2 C1 D1. With that, A1+A2 would be joined, but B1 and B2 were sent to separate jobs. Further, since B2 is the second part and would trigger the multiline, it might get appended to Z1, the last message that log_parser/1 received despite having no relation to it.
Even if we were using a single log parser, but had multiple shippers pushing messages in we could still have the same issue. For example, if shipper/0 has A1 A2 B1 B2 and shipper/1 has C1 D1, at some point they will send a batch, even if it's not all the events it has. So, the ingestor could receive/queue the first batch from shipper/0 with A1 A2 B1, receive a batch from shipper/1 with C1 D1, and then receive the next batch from shipper/0 with B2. The log parser would emit A1+A2, B1, C1, D1+B2 since C1 looked like an independent line, but then B2 looked like it needed to be joined.
To avoid this, we moved the multiline configurations to the log shippers. Typically, they know best what kind of logs they're watching and what general conventions the log emitters are using, so we actually found that to be a fairly straightforward process for us. Once we did that we no longer had to worry about maintaining that state once those messages were reaching the logsearch deployment.
So... all that being said, is this PR for the multiline codec the correct solution for your use case? Mainly, I guess, is have you been able to test and verify that this change works for what you need? If so, we can definitely merge it - I just want to make sure we fully understand why it was needed for maintaining it further down the road.

@bsnchan - any thoughts?

Closing due to inactivity.
@bsnchan, please comment/reopen if we can continue the discussion.


New version: ROCmDeviceLibs_jll v4.5.2+0

Autogenerated JLL package registration

Registering JLL package ROCmDeviceLibs_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/ROCmDeviceLibs_jll.jl
Version: v4.5.2+0
Commit: 2c95d958e65218a6e58f825847c67f4dc88f57eb
Revision on Yggdrasil: https://github.com/JuliaPackaging/Yggdrasil/commit/26b8d6bad3b5a0602297d95531fce25a5fe5f05d
Created by: @pxl-th

@vchuravy, this is the same issue as with ROCmLLVM :/
If you can take a look at it...


get the path right after reload page

Building my portfolio with nuxt http://buroponzo.nl/
if you click on a project it response well and navigate to
http://buroponzo.nl/gettingbetter
When I now reload/refresh the page (manually),
it's looking for images within the directory folder of this
route ->gettingbetter
All folders from routes are created with npm nuxt generate

How to fix this?! :)

Hi @merijnvanessen
Make sure you use / in front of your images and script path.
Example:
src="ponzoapp.js" -> src="/ponzoapp.js"
Otherwise the browser will resolve it relatively from your browser url.

The same with images, it looks like they're hosted in your /static directory, which can be reached by doing just /.
So this would work for the images:
/medium/gettingbetter_caseArtboard6-100.jpg

Awesome! Never stop learning! 👍
<img v-lazy="/preload/${block.content.image}" :data-srcset="/small/${block.content.image} 660w, /medium/${block.content.image} 1220w, /large/${block.content.image} 2000w"  class="image" />
refreshing . Thank you


Addition Refactorings

Renamed "java-app" to "java-exec" so that it matches the java:exec goal of the maven-java-plugin
Cleaned up generator names to not contain "."

LGTM

[merge]


Check failed: array->has_shape()

Hi,
First, Thanks for all your work! i'm struggling to export my tf model to tflite, seeing the error, i think i got 2 problems :

input format
unsupported ops
I can't find a way to solve this, maybe the issue is to do a more compatible tflite export when freezing the graph (close to something you did for export_tflite_ssd_graph.py but not sure i can make something equivalent for my case)

if you can help me for documentations and or good workaround...
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): googlecolab Window 10 x64 in conda venv
TensorFlow installed from (source or binary): binary
TensorFlow version (or github SHA if from source): 1.14.0

Provide the text output from tflite_convert
ConverterError: TOCO failed.  It would be helpful if you could inform us of how this conversion went by opening a github issue at https://github.com/tensorflow/tensorflow/issues/new?template=40-tflite-op-request.md
and pasting the following:
Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If those are native TensorFlow operators, you might be able to use the extended runtime by passing --enable_select_tf_ops, or by setting target_ops=TFLITE_BUILTINS,SELECT_TF_OPS when calling tf.lite.TFLiteConverter(). Otherwise, if you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: ADD, CAST, CONCATENATION, CONV_2D, DIV, EQUAL, EXPAND_DIMS, FILL, FLOOR_DIV, FULLY_CONNECTED, GATHER, LESS, LOG, LOGICAL_AND, MAXIMUM, MAX_POOL_2D, MINIMUM, MUL, PACK, RANGE, REDUCE_MAX, REDUCE_MIN, RESHAPE, REVERSE_V2, SHAPE, SPARSE_TO_DENSE, SPLIT_V, STRIDED_SLICE, SUB, SUM, TANH, TILE, TRANSPOSE, ZEROS_LIKE. Here is a list of operators for which you will need custom implementations: CTC_BEAM_SEARCH_DECODER, ComplexAbs, Enter, Exit, LoopCond, Merge, RFFT, Switch, TensorArrayGatherV3, TensorArrayReadV3, TensorArrayScatterV3, TensorArraySizeV3, TensorArrayV3, TensorArrayWriteV3.
Traceback (most recent call last):
File "/usr/local/bin/toco_from_protos", line 10, in
sys.exit(main())
File "/usr/local/lib/python2.7/dist-packages/tensorflow/lite/toco/python/toco_from_protos.py", line 59, in main
app.run(main=execute, argv=[sys.argv[0]] + unparsed)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 40, in run
_run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
File "/usr/local/lib/python2.7/dist-packages/absl/app.py", line 300, in run
_run_main(main, args)
File "/usr/local/lib/python2.7/dist-packages/absl/app.py", line 251, in _run_main
sys.exit(main(argv))
File "/usr/local/lib/python2.7/dist-packages/tensorflow/lite/toco/python/toco_from_protos.py", line 33, in execute
output_str = tensorflow_wrap_toco.TocoConvert(model_str, toco_str, input_str)
Exception: We are continually in the process of adding support to TensorFlow Lite for more ops. It would be helpful if you could inform us of how this conversion went by opening a github issue at https://github.com/tensorflow/tensorflow/issues/new?template=40-tflite-op-request.md
and pasting the following:
Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If those are native TensorFlow operators, you might be able to use the extended runtime by passing --enable_select_tf_ops, or by setting target_ops=TFLITE_BUILTINS,SELECT_TF_OPS when calling tf.lite.TFLiteConverter(). Otherwise, if you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: ADD, CAST, CONCATENATION, CONV_2D, DIV, EQUAL, EXPAND_DIMS, FILL, FLOOR_DIV, FULLY_CONNECTED, GATHER, LESS, LOG, LOGICAL_AND, MAXIMUM, MAX_POOL_2D, MINIMUM, MUL, PACK, RANGE, REDUCE_MAX, REDUCE_MIN, RESHAPE, REVERSE_V2, SHAPE, SPARSE_TO_DENSE, SPLIT_V, STRIDED_SLICE, SUB, SUM, TANH, TILE, TRANSPOSE, ZEROS_LIKE. Here is a list of operators for which you will need custom implementations: CTC_BEAM_SEARCH_DECODER, ComplexAbs, Enter, Exit, LoopCond, Merge, RFFT, Switch, TensorArrayGatherV3, TensorArrayReadV3, TensorArrayScatterV3, TensorArraySizeV3, TensorArrayV3, TensorArrayWriteV3.
here is the link to the shared notebook : https://colab.research.google.com/drive/1FhMBJHynRVfd_o-q2JH6Wn867YmnomjY
the frozen model .pb is available there : https://we.tl/t-1mwjdnJfxe
Thank you for helping, you're doing a great job
Raphael

It looks like you need to freeze the model first.

Thanks for helping, did you looked at the shared notebook, the model is already frozen to a *.pb file, did i missed something?

Sachin, do you mind taking a look on this (since this is related with exporting ssd graph)?  The vanilla response would be for you to implement custom ops for all these. However, we are adding better support for Control Flow (Merge, Switch, etc) & TensorList ops by next year, with an improved converter & builtin TFLite ops. However, these structures are usually required when you have ambiguous shapes in the graph. If you are training/exporting this model to a .pb, you could try 'freezing' some of these shapes?
Also, if binary size isn't a factor for you, you could also try using the Select TF Ops in TFLite option.
I know this isn't the ideal answer, but its usually better to work with a simpler model than try to convert a complex model, albeit at a loss of accuracy :-)

@srjoglekar246, thanks for helping me! :)
What do you mean with "you could try 'freezing' some of these shapes?" can you describe a bit please?, i'm not sure to get it
Also, with your suggestion, I tried to convert using  target_ops = [tf.lite.OpsSet.TFLITE_BUILTINS, tf.lite.OpsSet.SELECT_TF_OPS]
and i still get this error :
Here is a list of operators for which you will need custom implementations: CTC_BEAM_SEARCH_DECODER, Merge, Switch.
and if i set allow_custom_ops = True, i get this error :
Exception: TensorFlow Lite currently doesn't support control flow ops: Merge, Switch.
this come from the LSTM layer of my graph, do you now an implementation that doesn't have switch and merge ops?
Many thanks

Thanks for investing this Sachin, is ControlFlow v2 compatible with Tensorflow 1.14?
Before seeing your answer, I dug into into the differents LSTM components availables, and using BasicLSTMCell with Static_rnn seems to be a solution (still have to tune it) and doesn't use Merge/Switch.
With that, the only piece missing is the CTC_BEAM_SEARCH_DECODER op, i saw this issue :
https://github.com/tensorflow/tensorflow/issues/28045
So it seems its a fixed bug, but i still got the issue...
here is the updated graph in case you need it : https://we.tl/t-dKBgCsXhHt
Thank you for your time
Raphael


segfault when running process.sh

Trying to create the DAT file with a some extra data for a few japanese games. after adding the txt files and running setup.sh once, when I run process.sh I get a segfault.
`
vmu_blocks:186
accessories:5
genre:8
desc:Skate with the NHL's elite. More speed. More fluidity. More like ice. NHL 2K2 doesn't just pla like hockey, it feels like it. With lightning fast rushes, high impact checks, and snow-showering stops, you'll notice the difference the moment you lace 'em up.
Added[134] as MK51182
id:MK51059
num_players:1
vmu_blocks:80
accessories:4
genre:256
desc:The Experience Begins.  Real-time fighting with moves learned throughout the game - motion capture with real budo experts. Interact with a huge cast of characters with movements as intricate as a twitch of a finger.
Added[135] as MK51059
./process.sh: line 16: 118247 Segmentation fault      (core dumped) ${TOOLS}/metapack ${IN} ${OUT_META}
`
If I remove  MK51059.txt it will still segfault.

figured it out. I had empty "accessories=" lines, nothing instead of "0" or "None".


Updating domain for Archive.today

The domain archive.is now redirects to archive.li. Without updating this a consistent error this script gets stuck on is "Exceeded 30 redirects"

Thank you for updating the domain name.
I think it would be better if ArchiveNow identifies which domain is active before submitting requests to Archive.is. For example, as of now it is archive.li but this might change to archive.is or archive.today any time. I think this would be a better solution than hard coding.

This is already solved, so I will close it. Thx.


CSR request provide internal DNS before external, breaking route53 certificates requests.

Bug Description
I have noticed that the how-to guide about enabling TLS with trusted certificate by Let's Encrypt, as outlined here, is not currently working.
Specifically, when integrating route53 with traefik, an error is thrown by the route53 charm which I post here below:
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8: Exited with code 1. Stderr:
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 No key found for account<EMAIL_ADDRESS>Generating a P256 key.
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 Saved key to /tmp/.lego/accounts/acme-staging-v02.api.letsencrypt.org/enrico.deusebio<EMAIL_ADDRESS>unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 [INFO] acme: Registering account for<EMAIL_ADDRESS>unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 [INFO] [traefik-k8s/0, traefik-k8s-0.traefik-k8s-endpoints.history-server.svc.cluster.local, spark.deusebio.com] acme: Obtaining bundled SAN certificate given a CSR
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 Could not obtain certificates:
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:         acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "traefik-k8s-0.traefik-k8s-endpoints.history-server.svc.cluster.local": Domain name does not end with a valid public suffix (TLD) (and 1 more problems. Refer to sub-problems for more information.), problem: "urn:ietf:params:acme:error:malformed" :: Error creating new order :: Domain name does not end with a valid public suffix (TLD), problem: "urn:ietf:params:acme:error:malformed" :: Error creating new order :: Domain name contains an invalid character

The reason seems to be that traefik adds the internal dns before the external one in the CSR, which ultimately is picked by route53 to request a certificate to Letsencrypt (that turns down the request because of the "local" url).
This is indeed also shown in the logs of traefik, that reads
unit-traefik-k8s-0: 15:45:19 INFO unit.traefik-k8s/0.juju-log certificates:8: Creating CSR for traefik-k8s/0 with DNS ['traefik-k8s-0.traefik-k8s-endpoints.history-server.svc.cluster.local', 'spark.deusebio.com']

To Reproduce
Following the post should do the job
Environment
I'm running on EKS. For reference I post my YAML
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
    name: spark-cluster
    region: eu-west-3
    version: "1.27"
iam:
  withOIDC: true

addons:
- name: aws-ebs-csi-driver
  wellKnownPolicies:
    ebsCSIController: true

nodeGroups:
    - name: ng-1
      minSize: 3
      maxSize: 5
      iam:
        attachPolicyARNs:
        - arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy
        - arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy
        - arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly
        - arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
        - arn:aws:iam::aws:policy/AmazonS3FullAccess
      instancesDistribution:
        maxPrice: 0.15
        instanceTypes: ["m5.xlarge", "m5.large"] # At least two instance types should be specified
        onDemandBaseCapacity: 0
        onDemandPercentageAboveBaseCapacity: 50
        spotInstancePools: 2

which is created using
eksctl create cluster -f cluster.yaml

Relevant log output
nit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8: Exited with code 1. Stderr:
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 No key found for account<EMAIL_ADDRESS>Generating a P256 key.
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 Saved key to /tmp/.lego/accounts/acme-staging-v02.api.letsencrypt.org/enrico.deusebio<EMAIL_ADDRESS>unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 [INFO] acme: Registering account for<EMAIL_ADDRESS>unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 [INFO] [traefik-k8s/0, traefik-k8s-0.traefik-k8s-endpoints.history-server.svc.cluster.local, spark.deusebio.com] acme: Obtaining bundled SAN certificate given a CSR
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/01 15:45:20 Could not obtain certificates:
unit-route53-acme-operator-0: 15:45:20 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     	acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "traefik-k8s-0.traefik-k8s-endpoints.history-server.svc.cluster.local": Domain name does not end with a valid public suffix (TLD) (and 1 more problems. Refer to sub-problems for more information.), problem: "urn:ietf:params:acme:error:malformed" :: Error creating new order :: Domain name does not end with a valid public suffix (TLD), problem: "urn:ietf:params:acme:error:malformed" :: Error creating new order :: Domain name contains an invalid character
unit-route53-acme-operator-0: 15:45:21 INFO juju.worker.uniter.operation ran "certificates-relation-changed" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:44:25 INFO juju.cmd running containerAgent [3.1.5 8cff938c2d93f494ec722cccd46eb4dd3acf6807 gc go1.20.5]
unit-route53-acme-operator-0: 15:44:25 INFO juju.cmd.containeragent.unit start "unit"
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.upgradesteps upgrade steps for 3.1.5 have already been run.
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.probehttpserver starting http server on <IP_ADDRESS>:65301
unit-route53-acme-operator-0: 15:44:25 INFO juju.api cannot resolve "controller-service.controller-spark-cluster.svc.cluster.local": lookup controller-service.controller-spark-cluster.svc.cluster.local: operation was canceled
unit-route53-acme-operator-0: 15:44:25 INFO juju.api connection established to "wss://<IP_ADDRESS>:17070/model/385bbf0f-12e3-4d11-800e-0c19b49f47fe/api"
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.apicaller [385bbf] "unit-route53-acme-operator-0" successfully connected to "<IP_ADDRESS>:17070"
unit-route53-acme-operator-0: 15:44:25 INFO juju.api connection established to "wss://controller-service.controller-spark-cluster.svc.cluster.local:17070/model/385bbf0f-12e3-4d11-800e-0c19b49f47fe/api"
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.apicaller [385bbf] "unit-route53-acme-operator-0" successfully connected to "controller-service.controller-spark-cluster.svc.cluster.local:17070"
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.migrationminion migration phase is now: NONE
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.logger logger worker started
unit-route53-acme-operator-0: 15:44:25 WARNING juju.worker.proxyupdater unable to set snap core settings [proxy.http= proxy.https= proxy.store=]: exec: "snap": executable file not found in $PATH, output: ""
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.leadership route53-acme-operator/0 promoted to leadership of route53-acme-operator
unit-route53-acme-operator-0: 15:44:25 INFO juju.agent.tools ensure jujuc symlinks in /var/lib/juju/tools/unit-route53-acme-operator-0
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.caasupgrader abort check blocked until version event received
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.caasupgrader unblocking abort check
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.uniter unit "route53-acme-operator/0" started
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.uniter resuming charm install
unit-route53-acme-operator-0: 15:44:25 INFO juju.worker.uniter.charm downloading ch:amd64/jammy/route53-acme-operator-16 from API server
unit-route53-acme-operator-0: 15:44:25 INFO juju.downloader downloading from ch:amd64/jammy/route53-acme-operator-16
unit-route53-acme-operator-0: 15:44:25 INFO juju.downloader download complete ("ch:amd64/jammy/route53-acme-operator-16")
unit-route53-acme-operator-0: 15:44:25 INFO juju.downloader download verified ("ch:amd64/jammy/route53-acme-operator-16")
unit-route53-acme-operator-0: 15:44:30 INFO juju.worker.uniter hooks are retried true
unit-route53-acme-operator-0: 15:44:30 INFO juju.worker.uniter found queued "install" hook
unit-route53-acme-operator-0: 15:44:31 INFO unit.route53-acme-operator/0.juju-log Running legacy hooks/install.
unit-route53-acme-operator-0: 15:44:31 INFO juju.worker.uniter.operation ran "install" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:44:31 INFO juju.worker.uniter found queued "leader-elected" hook
unit-route53-acme-operator-0: 15:44:32 INFO juju.worker.uniter.operation ran "leader-elected" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:44:32 INFO juju.worker.uniter.operation ran "lego-pebble-ready" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:44:33 INFO juju.worker.uniter.operation ran "config-changed" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:44:33 INFO juju.worker.uniter found queued "start" hook
unit-route53-acme-operator-0: 15:44:33 INFO unit.route53-acme-operator/0.juju-log Running legacy hooks/start.
unit-route53-acme-operator-0: 15:44:33 INFO juju.worker.uniter.operation ran "start" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:45:18 INFO juju.worker.uniter.operation ran "certificates-relation-created" hook (via hook dispatching script: dispatch)
unit-traefik-k8s-0: 15:45:18 INFO juju.worker.uniter.operation ran "certificates-relation-created" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:45:18 INFO juju.worker.uniter.operation ran "certificates-relation-joined" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 15:45:19 WARNING unit.route53-acme-operator/0.juju-log certificates:8: Relation data did not pass JSON Schema validation: {'ingress-address': 'ae20c5df65e21415bb726281dfaa8b2a-1677762988.eu-west-3.elb.amazonaws.com', 'private-address': 'ae20c5df65e21415bb726281dfaa8b2a-1677762988.eu-west-3.elb.amazonaws.com'}
unit-traefik-k8s-0: 15:45:19 INFO unit.traefik-k8s/0.juju-log certificates:8: Creating CSR for traefik-k8s/0 with DNS ['traefik-k8s-0.traefik-k8s-endpoints.history-server.svc.cluster.local', 'spark.deusebio.com']
unit-traefik-k8s-0: 15:45:19 INFO unit.traefik-k8s/0.juju-log certificates:8: Certificate request sent to provider
unit-route53-acme-operator-0: 15:45:19 INFO juju.worker.uniter.operation ran "certificates-relation-changed" hook (via hook dispatching script: dispatch)
unit-traefik-k8s-0: 15:45:19 INFO juju.worker.uniter.operation ran "certificates-relation-joined" hook (via hook dispatching script: dispatch)

Additional context
N/A

Ah, acme_client does not recreate the CSR. The COMMON_NAME)[0].value is only for mapping the csr to the filesystem.
In that case changing the order of SANs in the cert won't matter.

Our design goal is depicted in a diagram here.
It seems that the scenario @deusebio is describing is as follows:

For in-cluster CA, we need to use cert_transfer with traefik, instead of tls_certificates.
For external CA, traefik needs to create a CSR over tls_certificates only with its external hostname. We should not add fqdn there (currently our cert_handler auto-adds fqdn).

Hi @deusebio,
Would you be able to retest by packing the charm from #204?

Sure thing! I'll do this straight away and report back ! Thanks for the  help and for looking into this @sed-i

After deploying the dev version of traefik from #204 and installing the ca-certificates, I'm still getting an error upon relation with route53. Not sure why, but even if the CSR is created correctly (see log about DNS below), route53 is still complaining because on the internal one (interestingly ACME is actually listing both dns, and the internal one fails):
unit-traefik-k8s-0: 10:07:13 INFO unit.traefik-k8s/0.juju-log certificates:8: Creating CSR for traefik-k8s-0 with DNS ['spark.deusebio.com']
unit-traefik-k8s-0: 10:07:13 INFO unit.traefik-k8s/0.juju-log certificates:8: Certificate request sent to provider
unit-traefik-k8s-0: 10:07:14 INFO juju.worker.uniter.operation ran "certificates-relation-joined" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 10:07:14 INFO unit.route53-acme-operator/0.juju-log certificates:8: Received Certificate Creation Request for domain traefik-k8s-0
unit-traefik-k8s-0: 10:07:14 ERROR unit.traefik-k8s/0.juju-log certificates:8: no relation on tracing: tracing not ready
unit-traefik-k8s-0: 10:07:14 WARNING unit.traefik-k8s/0.juju-log certificates:8: <class '__main__.TraefikIngressCharm'>.<property object at 0x7f88bef69680> returned None; continuing with tracing DISABLED.
unit-traefik-k8s-0: 10:07:14 WARNING unit.traefik-k8s/0.juju-log certificates:8: Provider relation data did not pass JSON Schema validation
unit-traefik-k8s-0: 10:07:15 INFO juju.worker.uniter.operation ran "certificates-relation-changed" hook (via hook dispatching script: dispatch)
unit-route53-acme-operator-0: 10:07:15 ERROR unit.route53-acme-operator/0.juju-log certificates:8: Exited with code 1. Stderr:
unit-route53-acme-operator-0: 10:07:15 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/11 10:07:14 No key found for account<EMAIL_ADDRESS>Generating a P256 key.
unit-route53-acme-operator-0: 10:07:15 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/11 10:07:14 Saved key to /tmp/.lego/accounts/acme-staging-v02.api.letsencrypt.org/enrico.deusebio<EMAIL_ADDRESS>unit-route53-acme-operator-0: 10:07:15 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/11 10:07:14 [INFO] acme: Registering account for<EMAIL_ADDRESS>unit-route53-acme-operator-0: 10:07:15 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/11 10:07:15 [INFO] [traefik-k8s-0, spark.deusebio.com] acme: Obtaining bundled SAN certificate given a CSR
unit-route53-acme-operator-0: 10:07:15 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     2023/08/11 10:07:15 Could not obtain certificates:
unit-route53-acme-operator-0: 10:07:15 ERROR unit.route53-acme-operator/0.juju-log certificates:8:     	acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Error creating new order :: Cannot issue for "traefik-k8s-0": Domain name needs at least one dot

Not sure whether this is an issue for trafik or route53 which, despite the CSR request, is picking wrong entries
@ghislainbourgeois @gruyaume

What's odd to me is that route53 is taking the CN, "traefik-k8s-0" and seemingly includes it in the SANs:
[INFO] [traefik-k8s-0, spark.deusebio.com] acme: Obtaining bundled SAN certificate given a CSR
Could not obtain certificates: Cannot issue for "traefik-k8s-0": Domain name needs at least one dot


[NL] add more legibility to bar chart legend

(tried black text, but the result is worse imo, since we have such strong colors for the background. changing the background would effect place explorer et al, so this feels safer for now).

nice!
another idea could be to try a low opacity dark background behind the text?

Yea, was trying to do that somewhat with the text shadow without altering the dom structure.. we'll see how well this works, if not we can go modify how we build the legend (maybe switch to disaster style legend).


Recovery from getToken IOException in onTokenRefresh()

Looking at the API docs, it looks like FirebaseInstanceId.getInstance().getToken() can throw an IOException. Shouldn't a robust app take that into account and have a retry mechanism at https://github.com/firebase/quickstart-android/blob/3b3903d9f3d88dde46503f72a0cd895798ff64a3/messaging/app/src/main/java/com/google/firebase/quickstart/fcm/MyFirebaseInstanceIDService.java#L38
?

was looking at the wrong getToken() definition, nevermind!


Drop Down object should cater for non-JS users

Closing this as this will be refactored and resolved in the soon to be released next major version: 3.0.0.


process#findExecutable() should not use sync fs

Looks like win32.findExecutable is being used from the renderer and has 3 occurrences of fs.existsSync() that should use the async variant instead. It should be possible to just return a promise from this method.
Feel free to move forward if you are not the owner of this method, I just went by git history.

@dbaeumer looks like I filed this in 2017 already (https://github.com/Microsoft/vscode/issues/34425). Is there a technical problem resolving this?

No technincal problem. I even think that this has no super high priority right now since the whole code needs to move out of the renderer anyways. This is independent of whether it is sync or async.

@dbaeumer oh ok, if it moves out of the renderer into the extension host than its less critical. Though I still think sync API should not be used if possible (I know we are not very good in other processes besides the renderer).


Add ability to create new container from existing one

Would like to be able to create a contain from a previously created container so I don't have to fill out all the same information again.
Should create container and be in create screen so I can change a field if I want to.

This request would also fall along with https://github.com/rancherio/rancher/issues/221.
Where we should create an option to clone/copy settings, but if you leave the container page, should all the settings be reset.

v0.22.0-rc1
Verified fixed - ability to  clone container feature added


fix import page

file was not saved before sending to repo

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for peaceful-meerkat-940447 processing.

Name
Link

🔨 Latest commit
f81a3c975f0dd6071b53e11f8319631cafd49b5d

🔍 Latest deploy log
https://app.netlify.com/sites/peaceful-meerkat-940447/deploys/640dda59114db10007f10ea0


toColourspace('cmyk') renders output incorrectly

I'm using the toColourspace('cmyk') to transform images in my app.
I found a few images (not all) that rendered incorrectly - missing a part of right image with white color.
Original version:

CMYK version - transformed by sharp:

Please advise.

Please can you provide a code sample that allows someone else to reproduce this.

@nusrick Were you able to make any progress with this? If not, please can you provide a complete, standalone code sample that allows someone else to reproduce this.

Closing due to inactivity but please feel free to reopen with the requested details if further help is required.


Feat/exemplar units - LESQ-250

Description

Adds new Exemplar Unit component

Issue(s)
Fixes #
How to test

Go to https://deploy-preview-1861--oak-web-application.netlify.thenational.academy
Click on _______
You should see _______

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner

:tada: This PR is included in version 1.233.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Abandon dithering on the device

Pre-render a large number of rotated, scaled, dithered images.
This inflates the binary quite a bit (currently a ludicrous 300 KiB up from about 40 KiB.)
But it's now possible to draw on every update with fairly consistent performance (in the simulator, so far.) If there's a hard limit on how big we can go, this isn't hitting it yet.
As a bonus, it's a lot easier to review and tweak the dithered images, since that code is now non-performance-critical Python and all the images are in the repo.
Presumably would want to render different images for different target device resolutions, but that seems feasible with this approach.

This also seems solid on the device, so merging


[Bugfix] Fix Mamba multistep

Implements advance_step for PlaceholderAttention so that Mamba and other attention-free models function with multistep scheduling.
Fixes the following error in buildkite
ValueError: Multi-Step not supported for attention backend: NO_ATTENTION. Set VLLM_ATTENTION_BACKEND to a value from [‘FLASH_ATTN’, ‘ROCM_FLASH’, ‘FLASHINFER’].

@youkaichao Of course I tested it locally! :laughing:


Please invite me to the GitHub Community Organization

Name
Chris Chen

I would like to be a part of this awesome community.


Related models should have the main entry locale too

WHY
BEFORE - What was wrong? What was happening before this PR?
If you have for example an HasMany relation where some fields of the related model are translatable, it will always display the default locale, ignoring the main entry locale.

So you are editing the main entry in french, it will save the related fields in the according language, but when displaying the main entry in french, the related fields are displayed in the default language (english).

AFTER - What is happening after this PR?
The related fields are edited in the same language as the main entry.
HOW
How did you achieve that, in technical terms?
setup the locale on model when fetching the related models from database.
Is it a breaking change?
I don't think so, it was not working at all.
How can we test the before & after?
Having translatable fields inside a relationship, there is nothing like that setup in demo, if you want I can create something there to test this.

Come on guys, I'm tired of adding this manually with every update, this with every update😀

@pxpm  just in case, I want to check if they forgot about it😀

@guleswine 🙃 🙃 Sorry sorry! I think what's preventing @tabacitu from merging this is that this should be merged with other PR that introduces the useFallbackLocale.
I will remove it from here, since it's not mandatory for this to work, to make this PR more appealing to @tabacitu merging skills 👍
Give me a sec I will push the change.

Ahhh... much cleaner! Thank you @pxpm , love it when it's so easy to understand what's wrong and what's the fix.
@guleswine we've merged it, it'll be available with a composer update starting Monday. Thank you for your patience 🙏 And the nudge 😉


Smooth scrooliing animation at item select

is there any possibility of smooth scroolling animation when i click on any item make him selected. i want at that time item will be scrolled smoothly to selceted postion.

Did you find a solution for this? If so, do you mind sharing?

@bearcat351 did not find any solution yet but i made a custom function to get x and y of screen then i scroll them at particular position.

Can you share your solution ?

@ankit02jindal @hatamiarash7  you ever find a solution for this?

@Cortlandd No. I have to use another library

@hatamiarash7 which?

@Cortlandd That's not a WheelView ... I tried another way to solve my problems

@hatamiarash7 I know. How did you go about solving it. Which library or implementation?


M 23.1 JDK 21 Q 3.x Warnings

build-and-run.log log should not contain error or warning lines that are not whitelisted. See /home/tester/jenkins/workspace/mandrel-linux-container-integration-tests/96a0edf0/testsuite/target/archived-logs/org.graalvm.tests.integration.RuntimesSmokeTest/quarkusEncodingIssues/build-and-run.log and check these offending lines:
Warning: The option '-H:ReflectionConfigurationResources=META-INF/native-image/io.netty/netty-transport/reflection-config.json' is experimental and must be enabled via '-H:+UnlockExperimentalVMOptions' in the future.
Warning: Please re-evaluate whether any experimental option is required, and either remove or unlock it. The build output lists all active experimental options, including where they come from and possible alternatives. If you think an experimental option should be considered as stable, please file an issue. ==> expected: <true> but was: <false>

Eventually whitelist...

There is an upstream netty PR that should fix this. In the meantime I agree that we should whitelist it.

@Karm Why is #203 not sufficient?

@Karm Why is #203 not sufficient?

On my Cosmo Communicator ™ now, might not have the full context pulled, but I think the whitelist was not complete, did not include container tests for other Q apps.

It would be good if steps to reproduce would be provided for issues being opened in the future :)

Whitelisted. Closing. https://github.com/Karm/mandrel-integration-tests/blob/master/testsuite/src/it/java/org/graalvm/tests/integration/utils/WhitelistLogLines.java#L121


:warning: Update / rework SPI module

This PR is rework/update of the processor's SPI module.

:warning: change control register layout
:warning: remove configurable transmissions size, SPI operations are fixed to 8-bit
rework interrupt configuration mechanism (new style 😉)
improve blockRAM mapping/inference (using FIFO with synchronous read access)

@akaeba Could you have a loot at the demo_spi_irq demo program?

@akaeba Could you have a look at the demo_spi_irq demo program?

yes i can check.

Driver is changed, but evaluation in simulator is pending.

Seems fine now.
Thanks for updating!


[ConfigTransformer] "An option with shortcut "n" already exists."

Hi,
I try to use config-transformer package (11.1.2) on a new project, but the command return the error: An option with shortcut "n" already exists.
I try previous version, 11.0.9, and it works fine.
I guess there is a conflict with default -n option for no-interaction.
Stack:
PHP: 8.1.9
Symfony: ^6.1
Composer: 2.3.10
Symfony CLI: 5.4.12

Hi,
Thanks for reporting :+1:
I didn't know there is a default option for --no-interaction. Could you send a fix PR to restore it?

The default -n shortcut come from Console package itself.
If I understand well Symfony behavior, the default options are set in \Symfony\Component\Console\Application::getDefaultInputDefinition then merged with options from command.


Custom library

Initial commit

Some sites wouldn't detect found or not result at the moment, still updating...
"G2G": {
    "errorType": "response_url",
    "errorUrl": "https://www.g2g.com/{}",
    "regexCheck": "^[A-Za-z][A-Za-z0-9_]{2,11}$",
    "url": "https://www.g2g.com/{}",
    "urlMain": "https://www.g2g.com/",
    "username_claimed": "user"
  },
  "Virgool": {
    "errorMsg": "\u06f4\u06f0\u06f4",
    "errorType": "message",
    "url": "https://virgool.io/@{}",
    "urlMain": "https://virgool.io/",
    "username_claimed": "blue"
  },
  "ebio.gg": {
    "errorType": "message",
    "errorMsg": "hasn't been claimed yet!",
    "request_method": "GET",
    "url": "https://ebio.gg/{}",
    "urlMain": "https:/ebio.gg",
    "username_claimed": "dev"
  },
  "Whonix Forum": {
    "errorType": "status_code",
    "url": "https://forums.whonix.org/u/{}/summary",
    "urlMain": "https://forums.whonix.org/",
    "username_claimed": "red"
  },

I think it good enough for use at the moment. Can you take a look of this @richiemann before merging and using on our provider

The search works fine with their use-agent, so then I revert the use of random-user-agent


Too many occurrence of the IllegalStateException on a part of devices.

Hello leanback development team,
I've found the issue of the IllegalStateException  occurred on only the LifeStick.
According logcats, it seems to be occurred in the leanback library.
Is it possibility that our implementation is mistaken? If so, could you how to fix it.
(Currently, our app has committed the BrowseFragment in the layout resource file)
Error details :
android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1434)
       at android.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1452)
       at android.app.BackStackRecord.commitInternal(BackStackRecord.java:707)
       at android.app.BackStackRecord.commit(BackStackRecord.java:671)
       at android.support.v17.leanback.app.BrowseFragment.swapToMainFragment(Unknown Source)
       at android.support.v17.leanback.app.BrowseFragment.replaceMainFragment(Unknown Source)
       at android.support.v17.leanback.app.BrowseFragment.createMainFragment(Unknown Source)
       at android.support.v17.leanback.app.BrowseFragment$SetSelectionRunnable.run(Unknown Source)
       at android.os.Handler.handleCallback(Handler.java:751)
       at android.os.Handler.dispatchMessage(Handler.java:95)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6077)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
#0. Crashed: main
       at android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1434)
       at android.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1452)
       at android.app.BackStackRecord.commitInternal(BackStackRecord.java:707)
       at android.app.BackStackRecord.commit(BackStackRecord.java:671)
       at android.support.v17.leanback.app.BrowseFragment.swapToMainFragment(Unknown Source)
       at android.support.v17.leanback.app.BrowseFragment.replaceMainFragment(Unknown Source)
       at android.support.v17.leanback.app.BrowseFragment.createMainFragment(Unknown Source)
       at android.support.v17.leanback.app.BrowseFragment$SetSelectionRunnable.run(Unknown Source)
       at android.os.Handler.handleCallback(Handler.java:751)
       at android.os.Handler.dispatchMessage(Handler.java:95)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6077)
       at java.lang.reflect.Method.invoke(Method.java)
       at

Same issue here. Please respond.

This sample has been migrated to a new location and updates are happening there. In addition, the new location can accept Pull Requests (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


Crash on server startup

We're currently experiencing this crash when trying to start our small modded server:
java.lang.NullPointerException: Ticking entity
	at joshie.harvest.crops.CropHelper.getCropDataAt(CropHelper.java:85)
	at joshie.harvest.crops.block.BlockHFCrops.feedAnimal(BlockHFCrops.java:390)
	at joshie.harvest.animals.entity.EntityAIEat.func_75246_d(EntityAIEat.java:42)
	at net.minecraft.entity.ai.EntityAITasks.func_75774_a(SourceFile:129)
	at net.minecraft.entity.EntityLiving.func_70626_be(EntityLiving.java:773)
	at net.minecraft.entity.EntityLivingBase.func_70636_d(EntityLivingBase.java:2189)
	at net.minecraft.entity.EntityLiving.func_70636_d(EntityLiving.java:577)
	at net.minecraft.entity.EntityAgeable.func_70636_d(EntityAgeable.java:155)
	at net.minecraft.entity.passive.EntityAnimal.func_70636_d(SourceFile:41)
	at net.minecraft.entity.EntityLivingBase.func_70071_h_(EntityLivingBase.java:2019)
	at net.minecraft.entity.EntityLiving.func_70071_h_(EntityLiving.java:295)
	at net.minecraft.world.World.func_72866_a(World.java:1964)
	at net.minecraft.world.WorldServer.func_72866_a(WorldServer.java:838)
	at net.minecraft.world.World.func_72870_g(World.java:1934)
	at net.minecraft.world.World.func_72939_s(World.java:1750)
	at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:619)
	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:709)
	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:387)
	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:613)
	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:471)
	at java.lang.Thread.run(Thread.java:745)

The full crashlog is here.

Ok, the crash is not instantly on startup, but occurs after the server has been running for a few minutes.

It will be related to cows/sheep trying to eat crops. Ideally keep animals a bit away from crops until I can fix it. To prevent the crash.

This crash is definitly related to #58
The server instantly crashes, as soon as the dirt block comes into view.

Okay I rewrote a bit of it. So HOPEFULLY it should no longer nullpointer. Since it's a server, I'm not sure how feasible this request is but could you possibly try it out this build (when it's done). And see if fixes the issue? (Worst case the crop should be like dead busy). Well that's if you haven't fixed the issue :p. Kind of a hard one to recreate it heh.
http://joshiejack.uk:8080/job/Harvest-Festival/job/1.10.2/89/

Looks like it works, thank you :+1:


Updated availability table

Outlook Mobile shipped to 100% GA WW, so updating table to reflect that.
Also updated the "default label" scenario in the availability table for web - this scenario is not coming soon, it's TBD.

@greg-lindsay - PR is ready for final review.
Thank you.
cc: @kenwith

The conflict was caused by the original table being split into two tables, but the edit here was done on the old single table.  However, looking at the public version https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-office-apps the changes in this PR already appear to be there, so I'll just close this PR.


Issue with enums wrapped as options

hopefully fixed with https://github.com/pjfanning/jackson-module-enumeratum/commit/e9c644cc5724bba30fa3814fd24bb2b9dd49185f

will be in 2.12.4 release


API rate limit exceeded when editing pages

We are still having issues with our NetlifyCMS instance where our team of editors keep running into issues updating content in our site (they are not technical people). When looking into it, I see a series of API rate limit errors in their consoles:
Pausing requests for 3600 second due to fetch failures: API rate limit exceeded for user ID 395641.

In digging further, these errors seem to happen when they try to load content via a relation widget in Netlify CMS. (see the three dots)

There are times when this works well, but for many, they experience so many issues uploading content that it can often take many attempts through the week to upload their content. It has been incredibly hard to debug what is happening. So far, my best guess is that it has something to do with authenticating with GitHub and the auth going stale.
Our config & setup

Our packages are up to date https://github.com/brooklynrail/brooklynrail-platform/blob/master/package.json
Here is our NetlifyCMS Config https://github.com/brooklynrail/brooklynrail-platform/blob/master/themes/brooklynrail/static/workflow/config.yml
Each of our staff members have GitHub accounts and have been registered in Netlify Identity
GitHub is registered as an External Provider in Identity, though seems to only work when we log in with our Identity user/pass
In our GitHub Org,

"Netlify Auth" has been added and configured as a third-party app in GitHub
Netlify has been added as a GitHub App

We are using GitLFS for all of our images

A theory
It could be that they log in at one point in the day they are logging in to our Netlify CMS, making a few edits, then leaving that browser window open. Then later in the day, they continue editing and at this point the CMS no longer authenticated with GitHub.
These are not people who will likely log in to GitHub during the day, nor are they checking out the code.
Any advice you can provide would be amazing 🎉

still experiencing related issue 4097

@jeremyzilar did you manage to resolve this? Any advice/workarounds/fixed?
Cheers!

It is very likely that you run into these https://docs.github.com/en/rest/rate-limit in scenarios of heavy usage of the github API

It is very likely that you run into these https://docs.github.com/en/rest/rate-limit in scenarios of heavy usage of the github API

The usage is supposed to be cached, and when this issue occurs it does not appear to be.
Of course if there is no local caching this would be expected

YOu can easily verify that issue at least by either checking the http headers or via "_token" (I believe this is the name) endpoint of github API

YOu can easily verify that issue at least by either checking the http headers or via "_token" (I believe this is the name) endpoint of github API

Verifying the rate limit being hit is not the issue though. The issue is exactly that - the rate limit being hit unexpectedly

The crux of the problem is that CMS is firing the API requests more often than necessary (on relation widget see #5920, but also elsewhere). GIT backends on the other hand have strict rate limits. Github for example currently has 5k/h but that can be increased to 15k/h if you go with one of their paid plans.
I'm aware of various efforts to optimize this by reducing the number of requests, but ultimately there will always be a hard limit.

Thank you @samo4 -- I will look at our use of the Relation Widget and maybe I can remove that. This is still happening, and our editors only have a few windows in the day when they can make edits, otherwise they are locked out. :/

@martinjagodic @demshy is there any progress on this issue? Quite troublesome for our workflow.

Back then, we fixed it on our fork and it seems to have helped. Since then, the fixes were already merged into Decap: https://github.com/decaporg/decap-cms/issues/6410
https://github.com/decaporg/decap-cms/pull/6902
Have you already tried using Decap 3.0? If you're still hitting rate limits, please inspect the network and maybe try to identify which sections are doing a ton of requests (possibly duplicate). Sharing your config would also help (to see if path regex fix applies to your case).

@demshy Oh that's great. I haven't tried Decap 3.0 yet. Looks like there shouldn't be breaking changes going from 2.10.79. I'll test it and report back. I'm deploying the CMS locally for now till I make sure the new version doesn't introduce breaking changes. Thanks a lot for pointing me to this.

Just updated and still receiving this.
Going to allow a few reload to see if it only occurs on the initial application load since upgrading to decap 3.0

@demshy Oh that's great. I haven't tried Decap 3.0 yet. Looks like there shouldn't be breaking changes going from 2.10.79. I'll test it and report back. I'm deploying the CMS locally for now till I make sure the new version doesn't introduce breaking changes. Thanks a lot for pointing me to this.

Forgot to report back. After upgrading, this issue happens much less than before. However, #7218 is now the new blocker.

Still experiencing rate limits.
Only 3 changes were made to pages before being limited.

I am not certain if this is related to relations on the pages, or the user utilising the Search field to find pages


Submittable Data Model

Here, we add a first cut for "submittable" items, i.e. items we expect external users to submit to us.
Main components of this PR include:

Schemas and types for submittable items
Permissions fixes and updates
Tests for the above + more robust coverage for various fixes and updates

Some of the primary ideas for the data model are:

Items to be submitted generally have a dependency chain via property requirements. For example, to submit files, one must also submit or have had submitted a file set.
All items to be submitted must have a submitted_id which serves as a unique identifier for the submitters
The majority of previously existing items (a.k.a. the "core" items) cannot be submitted by non-admins.
For now, there is no central or collecting item type, like a Case on CGAP or an Experiment on 4DN.

For testing, changes of interest include:

All items to be represented in workbook inserts, to serve as source for majority of tests instead of pytest fixtures.
Added broader, more generic testing to cover create permissions, schema expectations, unique keys, etc. rather than repeating similar tests for individual item types.
Deleted many existing tests due to changes above.

It looks like you should update the image schema to remove aliases and add submitter ID as it is referenced in histology (and maybe elsewhere?)


knife subcommand --help doesn't work as intended

:evilchef:
# chef --version
Chef Development Kit Version: 1.3.43
...
# chef gem install knife-acl
Fetching: knife-acl-1.0.3.gem (100%)
Successfully installed knife-acl-1.0.3
1 gem installed
# knife group --help
FATAL: Cannot find subcommand for: 'group --help'
Available subcommands: (for details, knife SUB-COMMAND --help)
...

Latest chefdk 4.3.13 don't gives above error but it does not show the expected result. It should filter out only knife group commands from list, but it lists all the knife command when we run knife group --help  also same is the result when we run knife acl --help

My bad it does give above error and then list the command

Fixed in #8915


New fixture - Robe-Robin-300E-Beam (with 5 new gobos)

This fixture has been modified greatly and the gobo references are local. The 5 new gobos were created by me from scratch in GIMP as there were no matching images available. A mixture of directories are used to source the gobos (other, GLP etc.).
Original author's post/manual link:
http://www.qlcplus.org/forum/viewtopic.php?f=3&t=8987
Gobos:
http://www.robe.cz/products/article/robin-300e-beam/#gobos

gobo00070 is Robe/gobo00029.png
gobo00072 is Robe/gobo00035.png
gobo00073 is Robe/gobo00027.png
gobo00074 is Robe/gobo00026.png
The only one really missing is gobo00072
If you can update the def an add just one gobo it would be great.
Thanks !

Hopefully this update has been posted correctly. There should now only be 2 new gobos.

Hey Robert, I decided to go the manual way.
Fixture is now online. Thanks !


[FEATURE] Composition for MySQL DB

Is your feature request related to a problem? Please describe
MySQL on RDS is very common and we should add an example of that.
MySQL on K8s should be easy to implement.
Describe the solution you'd like
MySQL on RDS
MySQL on K8s
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.

@nabuskey

MySQL on K8s

What you have in mind for this?
Like creating a composition that leverages the helm provider and deploy mysql using the mysql operator here https://dev.mysql.com/doc/mysql-operator/en/mysql-operator-installation-helm.html


Missing license on rubygems.org

https://rubygems.org/gems/cookiejar/versions/0.3.3
Licenses:
N/A

Fixed in d335a18

Thanks!


Fix misleading config in docker docs page

See: https://github.com/casdoor/casdoor/issues/901#issuecomment-1195509727

@leo220yuyaodog


Add usage for single-source example

I really love the work you're doing here, and want to use it in my own personal project!
However I'm currently getting to grips with the usage of this crate, and I'm struggling to get single-source to do anything once it's built. Would it be possible to have more examples to work off of, or have this example come with a bin target?
Many thanks for your work! And I would be happy to take a look at creating more examples once I've wrapped my head around it!

Thank you for your interest in my crate!
The print example is currently the only one that is fully executable.
I initially developed rust-cuda for necsim-rust, a neutral ecology model. It shows the full in-action usage of this crate:

https://github.com/juntyr/necsim-rust/blob/main/rustcoalescence/algorithms/cuda/gpu-kernel/src/lib.rs shows a full kernel. The crate is single-source, i.e. used both on the GPU and host, but still only contains the kernel for code clarity (this is roughly equivalent to https://github.com/juntyr/rust-cuda/blob/2a124b6f569eccecde633def0ea2b880c3d32fd6/examples/print/src/lib.rs#L22-L32

https://github.com/juntyr/necsim-rust/blob/main/rustcoalescence/algorithms/cuda/cpu-kernel/src/link.rs contains the explicit linking step for the pseudo-generic kernels that rust-cuda supports (i.e. the kernels can be fully generic but you currently need to manually instantiate all monomorphised variants of the kernel you want to use (this is roughly equivalent to https://github.com/juntyr/rust-cuda/blob/2a124b6f569eccecde633def0ea2b880c3d32fd6/examples/print/src/main.rs#L6-L8

https://github.com/juntyr/necsim-rust/blob/c8c3023a114aeacb97e130a60eff779f9c7cb539/rustcoalescence/algorithms/cuda/src/parallelisation/monolithic.rs#L252-L268 is where I actually launch the kernel from the host and do all of the memory transfers around it (this is roughly equivalent to https://github.com/juntyr/rust-cuda/blob/2a124b6f569eccecde633def0ea2b880c3d32fd6/examples/print/src/main.rs#L40-L48

If your kernel linking is ever so slightly complex, I'd recommend to also make the three-crate split (single-source kernel, linking, host) to improve compile times (since otherwise any change in the host code recompiles all kernel variants as well).
The important things to make sure everything runs, is to have the required CUDA libraries and the "llvm-bitcode-linker" and "llvm-tools" rust components installed, and to put the https://github.com/juntyr/rust-cuda/blob/main/examples/print/.cargo/config.toml file in the crate that contains your kernel.
I hope this helps a bit :) I could also have a look at your code to help you integrate rust-cuda if you'd like.


Refactoring install plugin script

Changes Proposed
Refactored the installation script to improve functionality, efficiency, and maintainability.
Additional Information
I have made the following changes to the script:

Replaced inconsistent variable usage with consistent usage of the name variable.
Introduced functions to encapsulate repetitive code blocks.
Handled errors gracefully and provided informative error messages.
Validated the availability of required dependencies.
Used consistent indentation and formatting throughout the script.
Separated concerns into separate functions for version detection, downloading, and installation.

Screenshots

Check List

[ x] The title of my pull request is a short description of the changes
[ ] This PR relates to some issue:
[ x] I have documented the changes made (if applicable)
[ x] I have covered the changes with unit tests

Thanks for the contribution!


[FEATURE REQUEST] Open on current window

Allow the user to open saved tabs on the current Safari windows instead of creating a new window.
Expected behaviour
Settings allow the user to choose between opening a new window or opening on current window. Clicking the "open" button next to a session should behave as the selected preference. option-click on the open button should toggle the inverse behaviour.

Yes, I would like to have this feature as well to limit the number of windows opened


File path length validation (NewPath)

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
There are limits on character length on file systems - for instance Linux is typically 255 but can be lower on ecryptfs-encrypted file systems - I have encountered this in libraries like HuggingFace Hub before and got it fixed so it can be parameterised from the file system programmatically (here https://github.com/huggingface/datasets/pull/3169):
import os

os.statvfs(new_file_path).f_namemax

(Source)

This would be a great addition to NewPath: I wasn't actually using it for validation but just had a very long filename (it originally came from an AI image generator whose image URL is the slugged text prompt) and when I saved it to disk my program crashed.
Of course I can check the filename length manually but:

this assumes I'm thinking of this edge case at all
since it is a quality of the file system then surely it comes under the same category of preconditions that we would want to be checked by NewPath

I took a look at the docs for NewPath but it doesn't seem to have any parameters I can set to this end, however when I create one it does correctly error!
>>> TypeAdapter(NewPath).validate_python((("foo")*100+".txt"))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/louis/miniconda3/lib/python3.10/site-packages/pydantic/type_adapter.py", line 208, in validate_python
    return self.validator.validate_python(__object, strict=strict, from_attributes=from_attributes, context=context)
  File "/home/louis/miniconda3/lib/python3.10/site-packages/pydantic/types.py", line 606, in validate_new
    if path.exists():
  File "/home/louis/miniconda3/lib/python3.10/pathlib.py", line 1288, in exists
    self.stat()
  File "/home/louis/miniconda3/lib/python3.10/pathlib.py", line 1095, in stat
    return self._accessor.stat(self, follow_symlinks=follow_symlinks)
OSError: [Errno 36] File name too long: 'foofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoo.txt'

This is an OSError though, whereas we would surely want it to emit a ValidationError
>>> TypeAdapter(NewPath).validate_python("package.json")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/louis/miniconda3/lib/python3.10/site-packages/pydantic/type_adapter.py", line 208, in validate_python
    return self.validator.validate_python(__object, strict=strict, from_attributes=from_attributes, context=context)
pydantic_core._pydantic_core.ValidationError: 1 validation error for function-after[validate_new(), lax-or-strict[lax=union[json-or-python[json=function-after[path_validator(), str],python=is-instance[Path]],function-after[path_validator(), str]],strict=json-or-python[json=function-after[path_validator(), str],python=is-instance[Path]]]]
  Path already exists [type=path_exists, input_value='package.json', input_type=str]

From the source:
https://github.com/pydantic/pydantic/blob/20c0c6d9219e29a95f5e1cadeb05ec39d8c15c24/pydantic/types.py#L1212-L1218
what this does is
Path(("foo")*100+".txt").exists()

which will raise the OSError
Note that trying to pathlib.Path.stat() or os.statvfs() the path is at risk of raising this, whereas we can more safely expect that the parent directory to be stat-able. Note that pathlib's stat function doesn't include the f_namemax though.
>>> p.parent.stat()
os.stat_result(st_mode=16832, st_ino=13238280, st_dev=58, st_nlink=53, st_uid=1000, st_gid=1000, st_size=16384, st_atime=1701773590, st_mtime=1701773589, st_ctime=1701773589)
>>> os.statvfs(p.parent)
os.statvfs_result(f_bsize=4096, f_frsize=4096, f_blocks=103473206, f_bfree=67819042, f_bavail=62544534, f_files=26353664, f_ffree=23318845, f_favail=23318845, f_flag=4102, f_namemax=143)
>>> os.statvfs(p.parent).f_namemax
143

So the safe way to check this in the routine then is:
        if os.statvfs(path.parent).f_namemax < len(path.name):
            raise PydanticCustomError('path_too_long', 'Path name is too long')
        elif path.exists():
            raise PydanticCustomError('path_exists', 'Path already exists')
        elif not path.parent.exists():
            raise PydanticCustomError('parent_does_not_exist', 'Parent directory does not exist')
        else:
            return path

This way we check that it's safe to call path.exists().
Note that this is only available on Unix (docs) so I would add a flavour check (I think an isinstance check is preferable to accessing _flavour directly).
        if isinstance(p, pathlib.PosixPath) and os.statvfs(path.parent).f_namemax < len(path.name):
            ...

Extension to other vfstat properties
While there, I considered if any other properties from vfstat (docs) would be useful (ignoring any that'd be too involved).
In particular f_flag flags related to the filesystem, and of these the read-only flag also seems relevant to check (after the existence check, for safety).
>>> os.statvfs(p.parent).f_flag & os.ST_RDONLY
0

Suggestion
In short I suggest adding an import (import os) to pydantic.types and modifying its PathType.validate_new method to:
        if isinstance(p, pathlib.PosixPath) and os.statvfs(path.parent).f_namemax < len(path.name):
            raise PydanticCustomError('path_too_long', 'Path name is too long')
        elif path.exists():
            raise PydanticCustomError('path_exists', 'Path already exists')
        elif not path.parent.exists():
            raise PydanticCustomError('parent_does_not_exist', 'Parent directory does not exist')
        elif isinstance(p, pathlib.PosixPath) and os.statvfs(path.parent).f_flag & os.ST_RDONLY:
            raise PydanticCustomError('path_readonly', 'Parent directory is read-only')
        else:
            return path

Impact
This would potentially be more restrictive but given the logic is sound then I would expect it would shift left (i.e. find invalid paths earlier) and not actually introduce new exceptions. It would change OSErrors to ValidationErrors (via PydanticCustomError) but I think this is desirable: would welcome your feedback.
Affected Components

[ ] Compatibility between releases
[X] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[X] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

@lmmx,
Should I add this issue to our 2.7.0 milestone? Would you be interested in working on this soon? 🚀

Sure thing I will add it to my development kanban: Xmas break came and went without a chance for this ! Busy for next week then can sprint on this

@lmmx,
Sounds great! I've added this to the 2.7.0 milestone :).

Hi @sydney-runkle, I would like to work on this issue. After taking a brief look at the code, I have one question for you and @lmmx (thank you for the detailed issue description, by the way): how should this error be handled elsewhere?
This file name too long error might occur with other methods of pathlib.Path as well, like .is_file() and is_dir(). I have tested this locally. Now, these two methods are used to validate class FilePath and DirectoryPath respectively. Take FilePath for example. Currently we have
def validate_file(path: Path, _: core_schema.ValidationInfo) -> Path:
    if path.is_file():
        return path
    else:
        raise PydanticCustomError('path_not_file', 'Path does not point to a file')

I'm thinking of changing this to
def validate_file(path: Path, _: core_schema.ValidationInfo) -> Path:
    if isinstance(p, pathlib.PosixPath) and os.statvfs(path.parent).f_namemax < len(path.name):
        raise PydanticCustomError('path_not_file', 'Path does not point to a file')
    if path.is_file():
        return path
    else:
        raise PydanticCustomError('path_not_file', 'Path does not point to a file')

Basically catching the same case but raise a path_not_file error instead of a path_too_long error. The logic is that if a file name is too long, surely that file cannot exist. Showing the path_too_long error in this case is not helpful because FilePath is a path that must point to a file. Telling users that the path is too long is like not answering the question properly: "Okay, the path is too long, but then what? I want to know if this path actually leads to a file! Oh... if the path is too long, then the file cannot be there, right...?" and this can be a bit confusing. Therefore, I think it's better to raise a path_not_file error in this case. Same for DirectoryPath. Does this make sense?

Hi @changhc,
Great questions. I'm inclined to raise a path_too_long error, given the source of the issue. I definitely understand your logic though - perhaps to shine more light on the source of the problem, we could modify the message associated with such an error to include a note about the f.namemax restriction?
I'm also wondering - is there any chance this is going to be a breaking change for folks? I don't think so, but if so, I wonder if it makes more sense to document this as a custom validator example instead of implementing a logical change under the hood.

@lmmx, what are your thoughts on the above?

Hey @sydney-runkle ooh this one fell off the task list, where were we 👾 By the way great talk at PyCon! 😄
You’re v welcome @changhc thanks for digging this back up!
Sure, extending to FilePath and any others is a good suggestion
Error code options
My intuition when using NewPath is that a validation indicates “yes you can make this path”, so in that case I’d definitely want to indicate the most precise reason why not, and be constructive on how to solve, so path_too_long it is.
Extension to FilePath
@changhc I hadn’t thought of extending scope here to FilePath but you’re right, it’s more precise to say that a file path doesn’t exist because the filename is too long to ever exist than to simply say “not found”. Yes I agree name_too_long is suitable here too.
Breaking: for who?
I can imagine a case in theory which would exist where an impossible operation being invalidated would change code behaviour, it’d be a case where Pydantic was used to lint operations but not actually carry them out.
We could break this category in turn down into 2 kinds:

those which actually carried out the operation (‘doomed’)
those which never got around to the impossible operation (‘got away with it’)

We are talking about breaking the latter kind of program, which I think is likely negligible in the real world. (TODO: look at grep.app to gauge how this is used, at least in open source code)
Moreover, Pydantic model validation is expected to produce side effects (i.e. all validation might raise), so as long as we are not changing the type of the error (i.e. ValidationError to something else), which we’re not (either bringing OSError into ValidationError, or just changing its error code) then I would not call this a breaking change myself, no.
Reproduction
I’m pretty excited by the new uv workspaces feature today like a lot of people, and just worked out a way to set up a PR demo here with a forked PR branch of the pydantic repo in a workspace package. I didn’t keep the work this structured last time which is part of why it didn’t get seen through to the finish line!
Repo is here, I’m fleshing it out with all of the above examples as TDD test cases now: https://github.com/lmmx/fp-len-validation-testing

I tried putting the suggested block in validate_new
        elif isinstance(path, PosixPath) and os.statvfs(path.parent).f_flag & os.ST_RDONLY:
            raise PydanticCustomError('path_readonly', 'Parent directory is read-only')

and made a demo read-only dir with mkdir foo then chmod -R 333 foo, to represent the parent of a new filepath
I'm not seeing it working, I'm going to take that one out and take the scope back to the file path length validation as per the title

@sydney-runkle Just to clarify, do you mean that you think we should raise path_too_long errors for FilePath and DirectoryPath as well?
I agree that for NewPath types (method validate_new) we should raise path_too_long errors. It's just that for FilePath (method validate_file) and DirectoryPath (method validate_directory) types I think it's better to "swallow" this path_too_long error and raise path_not_file/directory errors (@lmmx gets my point.)
About breaking someone's code, similar to what @lmmx mentioned, I think it's fine. Fixing this issue means we are bringing OSError into ValidationError. It will be a breaking change for someone who only handles OSError and lets the error get away but does not handle ValidationError -- the new ValidationError will be a surprise for them and maybe crash their program. However, I think this case is rather rare and I don't think it's that realistic. I assume that anyone using FilePath/NewPath/DirectoryPath is trying to validate paths. Then there might be

folks not handling any error: they let the program fail anyway when validation fails. This change is not a breaking change for them since the new ValidationError will fail the program as well.
folks expecting ValidationError: they want to deal with the error. As @lmmx mentioned, if they never hit this path too long error, this is not going to be a breaking change since they don't even know that OSError might be raised instead of ValidationError; if they hit the path too long OSError before, they would catch that and do something about it, but likely also terminate the program. For the latter group, this will change something but it should not be breaking since they will still get ValidationError and they are prepared for it.
folks expecting OSError only: they know that OSError might be raised and just want to catch it somehow...? Looking at the current code, the only case that the model gives either the path or OSError is when one always has paths in an existing parent directory and one ensures that the paths never collide (no path_exists or parent_does_not_exist errors.) A possible use case might be when one allows users to specify file paths to store files but appends some suffix like timestamp to ensure that filenames don't collide. They would then deal with OSError only since otherwise all input values are valid. Changing OSError to ValidationError will break their error handling. (Sorry if this sounds confusing. I don't even believe this is an actual use case at all.)

All in all, I don't think this is going to be a big breaking change. It does change the validator's behaviour and users who are aware of the issue and already doing something about it will be affected. I think the impact is minor, but I don't know how these people are actually dealing with this.

Looks like no major problems in the test (PR with just the initial suggested edit: #10207) besides what I assume is a FileNotFoundError being raised by test_new_path_validation_parent_does_not_exist in the test suite tests/test_types.py
    @staticmethod
    def validate_new(path: Path, _: core_schema.ValidationInfo) -> Path:
>       if isinstance(path, PosixPath) and os.statvfs(path.parent).f_namemax < len(path.name):
E       FileNotFoundError: [Errno 2] No such file or directory: '/nonexistentdir'

I resolved by updating to check the parent exists before os.statvfs'ing it.

@sydney-runkle Just to clarify, do you mean that you think we should raise path_too_long errors for FilePath and DirectoryPath as well?

Yeah I think Sydney is saying that it's reasonable to expect a user to reason through that "what does the file path too long have to do with anything...", I'm inclined to agree as it's more precise and gives the user a clearer idea of how to resolve it.

OK I've now put in this name length check on the file and directory validator methods, there's a bit of repetition here but they are each distinct cases and don't want to DRY it out too much.
M: pydantic/types.py
@@ -1263,14 +1263,18 @@ class PathType:

     @staticmethod
     def validate_file(path: Path, _: core_schema.ValidationInfo) -> Path:
-        if path.is_file():
+        if isinstance(path, PosixPath) and os.statvfs(path.parent).f_namemax < len(path.name):
+            raise PydanticCustomError('path_too_long', 'Path name is too long')
+        elif path.is_file():
             return path
         else:
             raise PydanticCustomError('path_not_file', 'Path does not point to a file')

     @staticmethod
     def validate_directory(path: Path, _: core_schema.ValidationInfo) -> Path:
-        if path.is_dir():
+        if isinstance(path, PosixPath) and path.exists() and os.statvfs(path).f_namemax < len(path.name):
+            raise PydanticCustomError('path_too_long', 'Path name is too long')
+        elif path.is_dir():
             return path
         else:
             raise PydanticCustomError('path_not_directory', 'Path does not point to a directory')

To be clear, the parent directory of a file path is being checked in the file validator case here only to get the path length limit (which can change for different paths on a drive even, so you can't check anything 'in general', the parent directory is your only way to reliably tell).

@changhc raises a good point: the new path could rely on parents (it's not our business how the user plans on making the new path)

I guess we need to catch OSError in the validation methods anyway. The following will fail this check:
>>> p = PosixPath("a"*1000 + "/" +"x"*1000)
>>> p.parent.exists()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/changhc/.pyenv/versions/3.12.3/lib/python3.12/pathlib.py", line 860, in exists
    self.stat(follow_symlinks=follow_symlinks)
  File "/home/changhc/.pyenv/versions/3.12.3/lib/python3.12/pathlib.py", line 840, in stat
    return os.stat(self, follow_symlinks=follow_symlinks)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 36] File name too long: 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'

and this brings us back to the original problem. :(

via PR review comment

I put in a new example / test case for this here: https://github.com/lmmx/fp-len-validation-testing/blob/master/examples/new_long_dir_and_file_names.py

I've no idea what happened but somehow a bunch of datetime tests just broke :(
I can only think maybe it was the else raise part, but very confused now.


How to get width and height of original img?

could u offer some specific exmaple api about how to get img infomartion,is it has to use pro version?

Hey @leopold1989!
Getting an image info is a Pro feature, yes.

Getting at least the dimensions/ratio is very useful for static site generators. There already is a way to get this information from headers if EnableDebugHeaders  is enabled. The imagemeta package is already public. @DarthSim Do you consider open-sourcing this as an endpoint? Or allowing a contribution without a fork?
For my use case, Thumbor has /meta/ info, and this missing feature prevents me from switching to imgproxy. I'm using thumbor-wand-engine because of HEIC support and experimenting with thumbor-vips-engine.

@Tymek Sorry, but we won't add the /info endpoint to the OSS version.
Also, even with all my love for imgproxy, I believe that using vips directly or via Sharp at build time is more suitable for static site generators.


updated NER version and tweaked tests

Reviewers:

[ ] @madisonmay
[ ] @anneCarlson

What's the purpose of the PR?

Updates version number of ner.
https://trello.com/c/voWeqH80/1986-3-ner-updated-in-client-libs-default-version
Description of changes

Notes to reviewers

Keep in mind while reviewing code:

Is relevant code tested?
Are added functions/methods documented?
Separation of concerns (SOC)
Don't repeat yourself (DRY)
Limit the number of positional arguments
Is function/method length reasonable?
Can code be broken down into smaller components?
Where do added functions/methods belong?
Are variable names descriptive?
Are errors handled appropriately?
Can logic be simplified?
Does the code make sense in context? (expand the diff)

This PR already exists #181

Oops!


Handle decimal fields in singer-check-tap

We should change singer-check-tap to handle decimal fields in a way similar to target-stitch. https://github.com/singer-io/target-stitch/blob/master/target_stitch/init.py#L10

Anyone can feel free to re-open this if they find time to work on it.


Features Wishlist

After having some trouble earlier getting this to work, (#21, #22) I've returned to this on a different computer & with node 12 instead of 14 and it works great. Now that I've got this working, there's nothing holding me back from using Love2D more, and I think I'd like to contribute to this library to make it as good as it can be. So, I'm making an issue with a short list of the features I'd like to implement:

Ability to specify a custom theme at build time, so you don't have to edit the built .html or .css files each time you rebuild
A "serve" option, where after you build it starts a little HTTP server locally so you can view your output files in a browser
A "watch" option, where it'll watch the filesystem for changes & rebuild each time it detects one.
When you run it on a directory, an option for ignoring files (such as the .git folder) and leaving them out of the build

Nice, but it might be better to open one issue per feature.


Aerogear unified push server integration is outdated

Aerogear unified push server integration is needed to be updated. In new code android client will receive config for connection from REST endpoint instead of hard coding it in app

I will do it @garg-anuj

That will be too big chunk to be taken in initial stage. Lets break in chucks for that

That will be very helpful.

What is the first task?

Getting some understanding of https://github.com/jboss-mobile/unified-push-helloworld for now
Then we will first make hard coded system work again before going to next stage

OKAY @garg-anuj

@shubhamvashisht @garg-anuj ping me if you need some help on it

@danielpassos Surely we will need your help :)
I was just waiting for monday to come


Remove patch for Omnibox URL formatting

In wchen342/ungoogled-chromium-android/issues/21 someone mentioned that in vanilla chromium, if #enable-mark-http-as is enabled then the protocal part (https://) will be hidden, while only http:// will be shown as a warning. Supposedly it will be better this way and the reasoning is in the mentioned issue.
However in ungoogled-chromium there is a patch (I believe it is disable-formatting-in-omnibox.patch) explicitly disables that behavior. @Eloston I wonder why the patch is included in the first place? Is there a conclusion on which way is actually better?

One thing to note is that upstream Chromium  (desktop only) will get a context menu option for toggling the elision too, so the patch could be removed either way. https://bugs.chromium.org/p/chromium/issues/detail?id=1061576

I wonder why the patch is included in the first place?

I made that patch years ago, possibly even before I created the ungoogled-chromium project. Things were more naive and experimental back then.
Considering that Google is adding an option to show the full URL (thanks @Madis0 for linking the crbug), I see no reason to keep this patch. However, since this patch has been in ungoogled-chromium for so long, I think we should keep it until Google's changes land in stable Chromium (which will be Chromium 84?) since it's the only way to show the full URL right now.

Update: According to https://bugs.chromium.org/p/chromium/issues/detail?id=1061576#c29, it seems like we'd need a patch to always enable the context menu option because of field trial testing. So it's probably easier to hold onto disable-formatting-in-omnibox.patch until Chromium permanently enables the feature.

What is the current state of this issue?


Bring npm package up to date with Github repo

The current version of the npyjs npm package seems to be behind the Github repo version, updating the npm package to match the repo version would be helpful.
You could consider automating the process of publishing to npm through Github actions (e.g. when pushing code or when accepting pull requests).

@jhughes982 — thanks for bringing this to my attention! I just released v0.2.1 to npm and will be working on getting this automated via github actions in the near future!


Frontend compatible with Zep

Sorry for being slightly off-topic. Discussions are not enabled on this repo, so figured I'd file it here. But please close if you feel like this is not the place for this.

What I wanted to discuss is how to build a frontend app for this backend. I know there are many options and frameworks. But if anyone has built anything and knows solid building blocks for this, please share. In particular interested in the React-based approaches to build ChatGPT-like chats, mostly for internal use.

@moltar Have you taken a look at https://flowiseai.com/?

Yup, looked at it a while back, but I do see it has Zep integration! That's cool, will try again. Thanks.


[Core] Upgrading System.Diagnostics.DiagnosticSource to 5.0.0 (netcoreapp2.1)/ 6.0.1

This is the first piece of resolving #33683. Unfortunately, given the dependencies between packages, I don't think it's possible to upgrade the dependency and use the new types in the same release, or at the very least in the same PR. I think we may need to release with the upgraded dependency first and then merge in the rest of the work in this PR: https://github.com/Azure/azure-sdk-for-net/pull/37149.
Initially, there were concerns about PowerShell and functions integrations when upgrading this dependency. After doing some research, the most recent versions of PowerShell 7 depend on the newest version of the System.Diagnostics.DiagnosticSource  (7.*), so upgrading this dependency should not impact PowerShell integration.
In order to support both netcoreapp2.1 and the new types, we need to multitarget with 5.0.0. System.Diagnostics.DiagnosticSource 6.0.1 has a transitive dependency that does not support netcoreapp2.1.  However, System.Diagnostics.DiagnosticSource 5.0.0 is deprecated, so we shouldn't take a dependency on that version anywhere else.
There are also some changes here to MessagingClientDiagnostics. This file was causing pipeline errors that needed some simple to updates to fix.
This also contributes to: https://github.com/Azure/azure-sdk-for-net/issues/35572
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.

Were we able to talk to someone from PowerShell to confirm that this change is okay for them?

Were we able to talk to someone from PowerShell to confirm that this change is okay for them?

I was able to touch base with someone on their team and they weren't aware of any issues that would arise from this change. The newest version of PowerShell 7 takes a dependency on System.Diagnostics.DiagnosticSource 7.0.2.


[FY25.1 Sprint 5] Add 3-7 additional flight maps to CASEI

This issue follows https://github.com/NASA-IMPACT/admg-casei/issues/711
Context
Back in FY24.1, we started visualizing flight paths for campaigns on CASEI. We started with 5 (see epic: https://github.com/NASA-IMPACT/admg-casei/issues/576) and have since expanded to ~8 (see YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR).

Example of a flight map for a campaign
As of FY24.4, we have published 44 campaign flight paths.
Known Challenges
We learned through past efforts in trying to automate the data collection and visualization process that currently it is NOT possible to fully automate this process for these reasons:

Inconsistent data formats as in NASA's case airborne data ownership is split across 12 DAACs that all do things a bit differently
Different ways to define measurement variable names. This might not seem like a big deal but it really makes it hard/slow to get buy-in when building out features quickly as terminology is for queries and UI filters gets challenged back and forth. There are initiatives on streamlining language, for example the official GCMD science keywords (which is a string of keywords) but each DAAC also has their own views and it’s an ongoing discussion.
Incomplete data. To get the full set of historical data to even visualize flights (let along instruments on each flight deployment), in many cases you’ll need to manually look for data that’s lock in PDFs still or old canned films for example that are not digitized. This is what the ADMG data curators have been doing and filling in for CASEI

Goal

We will continue to collect and visualize campaigns in batches (of around 3-6) because each campaign may need some manual data fixes.
We will incorporate fixes to common data issues along the way, and continue to learn about the extent to which we can still create a pipeline for visualizing nav data in the cloud without having to do it locally and save out GeoJSON files

Acceptance Criteria

3-6 additional nav data sets saved as YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR
Static locations for those campaigns https://docs.google.com/spreadsheets/d/17v-ZfeWoPZoCAVSs57Y3Q1gKUe6S49fZ8rC2KOO_myY/edit#gid=1924471089
3-6 flight tracks visualized and deployed to CASEI in staging
Deploy from staging to production

@als0076 Two new campaigns to be reviewed:
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/PODEX
http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/Polar Winds/
Let me know if it looks good.

@willemarcel Sorry for the delay. I was at a conference last week, but they both look good!